On 29/08/2011 22:55, Flávio Etrusco wrote:
On Mon, Aug 29, 2011 at 6:08 PM, Graeme Geldenhuys
<[email protected]> wrote:
And from what I remember there is still a bug in the LCL's GTK2
version. If you did code navigation (Ctrl +Click), then click on the X
in a tab, it closed all other tabs except for the one you clicked on.
:-( That was a very annoying bug I trigger often.
The Ctrl key state was "sticky" for some reason. I reported this
problem, but can't remember if it was ever fixed - i haven't tried
trunk in ages. I have since been using Ctrl+F4 (close file) instead.
The bug is still present in trunk. I stepped on it while looking at
the AltGr support (regarding the SynEdit column-mode discussion for
which a follow-up is still in my drafts :-$ ).
The LCL use a hook to peek into key messages and "caches" ShiftState,
it's in my to-do to look at using gdk_event_get_state() or
gdk_window_get_pointer() instead...
Afaik, quering always was an issue on gtk especially if used on remote
display, as it is (so I was told) slow on some systems)
I do know, that there was some work done (as I was involved), that leads
to updating the cache in mouse events (move up down, IIRC) => and on
platforms that I tested this solved the sticky ctrl issue (including
when focus was moved away from the app)
IMHO the original report was that ctrl was sticky when the app lost
focus while ctrl was pressed. I do not know about the code navigation
part, making ctrl sticky => first time I hear this => so I can't comment
on this.
Also I have not lately tested any of this, so I can not comment if
anything was re-introduced.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
