Thank you. Thinking about it, maybe we could solve this problem plus the "fireevent" feature by introducing K_* code(s) (f.e. K_HBSYSCLOSE) and simply passing it/them to Harbour just like we do for keyboard and mouse event. Such K_* codes could be enabled by new INKEY_* mask bit (f.e. INKEY_HBEVENTS).
In such way we could migrate and drop current HB_GTI_NOTIFIERBLOCK solution, which is quite problematic as it blocks the introduction of screen refreshing thread in GTWVT. If screen refreshing thread is in place, we could retest if LAYERED feature is still needed (probably it is, but not so badly as now). Of course this would create slight incompatibility with previous Harbour versions, but I assume notifierblock is not very widely used and old method can relatively easily be updated to use custom Inkey() wrapper or simple SETKEY() method. Any opinions on that? (or anything I missed? I'm not sure why we haven't done it this way in the past) Brgds, Viktor On 2010 Apr 6, at 11:16, jara...@users.sourceforge.net wrote: > Revision: 14275 > > http://harbour-project.svn.sourceforge.net/harbour-project/?rev=14275&view=rev > Author: jarabal > Date: 2010-04-06 09:16:30 +0000 (Tue, 06 Apr 2010) > > Log Message: > ----------- > 2010-04-06 11:15 UTC+0200 Xavi (jarabal/at/gmail.com) > * harbour/src/rtl/gtwin/gtwin.c > % Reverted back the changes. > > Modified Paths: > -------------- > trunk/harbour/ChangeLog > trunk/harbour/src/rtl/gtwin/gtwin.c > > > This was sent by the SourceForge.net collaborative development platform, the > world's largest Open Source development site. > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
