Hi,

I've started the v1.2 release cycle, and created a 'release-1.2' branch. This means there is a feature freeze on that specific branch, and only bugfixes will be applied. Please test and let me know in the support newsgroup of any bugs you might find.

fpGUI repository on Github:
git clone https://github.com/graemeg/fpGUI.git

Info on connecting to the NNTP news server for support: http://fpgui.sourceforge.net/support.shtml

Many thanks.

Regards,
- Graeme -

Graeme Geldenhuys wrote

I've started the v1.2 release cycle, and created a 'release-1.2' branch.

Sounds rather great to me as I would be able to use TThread.Queue in a modified Lazarus Widget Type to create Application.QueueAsyncCall (in a test this already does work fine for me).

While for me this is not an obvious issue, someone mentioned that Application.QueueAsyncCall based on TThread.Queue will not be not completely compatible to Application.QueueAsyncCall in other Widget Types, as - seemingly for Delphi compatibility - TThread.Queue does not queue the call but call the function immediately in the (supposedly close to never used) case that it's called from the MainThread, while all current Application.QueueAsyncCall implementations always do the queuing.

Does it make sense to do something about this issue, or do you think it's enough to just document that in the planned Widget Type works that way ?

-Michael

modified Lazarus Widget Type to create Application.QueueAsyncCall (in a test this already does work fine for me).

Huh? What does fpGUI have to do with TThread.Queue?! O.o

Regards,
Sven

Sven Barth wrote

Huh? What does fpGUI have to do with TThread.Queue?! O.o

Ooops sorry :-(

As this was in the fpc forum, I thought it would be about fpc itself, silly me ignoring typing faster than thinking and that this is not the fpc-devel forum.

-Michael