On 01/12/2011 05:46 PM, [email protected] wrote:
YOU would presumably use it, since you seem to have an interest ?
Not really. I did have personal (company) interest for this when I
started the research, right now I'm only trying to learn more about the
topic and to help improving the (IMHO) obvious shortcoming of the
(generally really amazing) project. I feel that right now the evolving
fpGUI Widget Type might offer a platform for a n implementation in a
less legacy-orientated way.
Thinking about your comments, yesterday in the evening I have been
thinking about how I might be able to really provide a patch, to make me
feel a little bit better. So I did plan to do a patch that provides
TThread.Queue (as requested in a bugtracker article). This could easily
be based on TApplication.QueueAsyncCall.
But even that small patch (some 10 lines) is impossible to do due to
political reasons:
the TThread class is defined not in Lazarus but is part of the fpc
distribution and humble me can't hope for a simultaneous change in both
projects, and I can't be sure about the implications when using the
changed TThread class in non-Lazarus projects.
Maybe we could do something like
TThread = class(classes.TThread);
but I don't know if this is not a depreciated style or even impossible.
Once implemented, maybe we could be convinced that such an approach
may bear
fruits.
Yep . This is why I do hope for Graeme to do an fpGUI Widget Type
implementation according to theses lines (to which I maybe can offer
some help) and this is why I feel like discussing this here.
Your refusal to come up an implementation that works is strange (to
put it mildly)
Sorry that you think this, I tried to explain, why I think that it's
just impossible for me to start this project on my own.
-Michael
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
