[fpc-pascal] Why opening a file for write fails in fpc 2.6?

[Giuliano Colla]

Il 01/11/2012 13:09, Graeme Geldenhuys ha scritto:
> On 2012-11-01 11:49, Giuliano Colla wrote:
> Now I'm looking forward with interest to CustomDrawn, which should
> I've recently (about 3 weeks ago) looked at LCL-CustomDrawn. It is still
> years away form being usable in production code. Simple things like the
> default Cut/Copy/Paste popup menu in text widgets don't exist. Tabbing
> in reverse order between widgets don't work etc. The more you look the
> more issues you will find in LCL-CustomDrawn.  This doesn't mean
> LCL-CustomDrawn in bad, it just means it is not near being ready to be
> used in real world applications.
>
I fully agree with you. CustomDrawn is at a very preliminary stage. I'm 
not even sure that the current implementation of LCL-CustomDrawn will 
ever lead to a usable thing. The approach is a brute force one: just one 
window for form, and redraw all the widgets on the full form each time 
something changes. Even cursor blinking is achieved by redrawing the 
full form. You can imagine how slow everything becomes when your window 
has a reasonable size, and is populated by a reasonable number of widgets.

That's the problem of many open source projects. They're mostly created 
by developers which think to their applications, and take care primarily 
of what they need. CustomDrawn was originated by Felipe, who's mainly 
interested in his Magnifying Glass project. Once he manages to make it 
work on his target platform, he's more or less finished.

But the same holds true for me. In my applications I don't use neither 
the Cut/Copy/Paste popup menu, nor tabbing (forward or reverse), so you 
may bet that if I contribute to CustomDrawn, be it the current 
implementation or a fully new one, those features will end up quite low 
in my ToDo list.

That's the main reason I look with more interest to LCL than fpGUI. 
Simply because LCL provides already implemented much more features I 
need with respect to fpGUI, (at least up to the last time I evaluated 
fpGUI).
When the time comes that I'm really forced to abandon Kylix, then I'll 
try to see if it's more work to implement what I need (and which won't 
certainly be there) on CustomDrawn (most likely stealing quite a lot 
from fpGUI), or to contribute to fpGUI, in order to get what I need.
For the moment I've devoted the little time I have available to some 
contributions to CustomDrawn, because I have more confidence with LCL 
environment, and this makes things easier for me.

Giuliano