[4692 win] gw paste broken

[Luc[as]]

When I cut or copy one or more cells in the glyph window, I can't paste them!?
Huh. why didn't I notice this before? Will it work again tomorrow?

[Luc[as]]

No, same as yesterday, pasting glyphs in GW does not work

[Luc[as]]

Have you noticed I am actually trying to use this beta :-)

[Luc[as]]

In 504 copying and pasting of cells in GW doesn't work either. A mystery, time to reboot.

[Luc[as]]

No, I just had to quit CorelDraw :-)
And then after an hour of working in FLSWin 4692 it just crashed...

[Luc[as]]

Rebooted the computer, after some hours of copying and pasting, FontLab stops copying and pasting glyphs in the GW again. Mystery or mighty memory leak?

[Luc[as]]

When in GW, cutting more than some amount of paths or points seems to crash FL fairly consistently

[Luc[as]]

cutting more than around 4500 points in a GW crashes FLS.

[Luc[as]]

In the font file I'm working on I found several glyphs with identical glyph names. Not good.
When I am in the index mode, copy a glyph named p.001 and paste it, I get another glyph with the same name.
The ever reoccuring double glyph name problem should have been fixed 538 releases ago ;-)
When I paste again FL starts numbering correctly: p.002 p.003 etc.

[Sandy JMA]

Ever get the feeling you're talking to yourself? 

[Luc[as]]

Yes, all the time.
But Adam ensured me that FontLab People (managers, programmers) read all the mails.
However, it seems very much like they don't :-)

[Luc[as]]

I've even offered them to answer in Russian :-)

Still having trouble with copying and pasting glyphs in GW.

And why do FontLab generated CJK fonts turn up as gibberish in CorelDraw X5?
Custom CMAPS and 2nd pane Unicodes are driving me nuts.
Will it be solved in Corel X6?
It's amazing how many software licenses I bought just to find that some app does something wrong with fonts.

[Luc[as]]

No, not solved in CorelX6, it could be a FontLab issue then...

[Adam Twardoch (FontLab)]

We do read it then. But our developers are working on the backlog of existing, logged bugs. We want to resolve these before addressing new ones.

However, this is still the best place to report these problems, and we're certainly monitoring it. No response doesn't mean that we don't read it.