Re: How to grab key combination event in GDK?

[salsaman <salsaman gmail com>]

On Sat, Feb 4, 2012 at 14:07, Paul Davis <paul linuxaudiosystems com> wrote:
> On Sat, Feb 4, 2012 at 11:41 AM, salsaman <salsaman gmail com> wrote:
>> So whats the replacement ? Set key event handlers for every single window ?
>>
>> That makes no sense. Why remove a function which works perfectly well,
>> which people are relying on ?
>
> gdk_window_add_filter (NULL, ....) works for all windows.
>
> anyway, key snooping has not been removed and its not *officially*
> deprecated even in gtk3 (yet). furthermore, deprecation is not
> removal.
>
>> Im sorry, but all I have seen so far of GTK+3 is function after
>> function being removed, little or no documentation explaining the
>> replacement, no reasoning given as to why any function has to be
>> removed.
>
> i live in an interesting place. on the one hand, i'm the lead dev of a
> big, complicated project that uses GTK. as such, i tend to have the
> same kind of judgement that you're expressing here. but on the other
> hand, from time to time i also get involved with OS X support in GTK,
> or trying to fix very specific issues with GTK, which gets me much
> closer and involved with the core GTK team. far from being the raving
> crazed fools that you're sort of portraying them to be,  i find that
> they actually have a vision, and that their decisions have clear
> rationales behind them. do they spend documenting all that stuff for
> developers? no. why not? because there is only so much time in a day,
> and that time is arguably better (and certainly more enjoyably) spent
> actually doing stuff.
>
> i know that with ardour, we rarely (if ever) talk about development
> plans on our "development" mailing list anymore, except for a few
> topics where for some reason broader input is needed. almost all of
> our development discussion, both with users and other devs, is now on
> IRC. GTK is much the same way. if you're on the channel, you'll see a
> lot of discussion about stuff; if you're on the ML you'll see
> occasional communications about big things that could and should take
> some time.
>

I'm sorry yes, the timing of your message was bad - I just had a very
similar issue with another function being removed [
gdk_pixbuf_render_pixmap_and_mask ] apparently with no thought given
as to what would replace it, or if there was, certainly no
documentation about it.

And really, I spend far too much time already testing and writing
obscure workarounds for interface issues. I would rather be
concentrating on what my app is intented to do - editing and playing
video. Just as I am sure you would rather be concentrating on audio
production in ardour. The toolkit should be there to solve problems,
not require constant attention to be always upgraded like some kind of
demented tamagochi.


Despite this I think GTK+ is still the best toolkit out there which is
why I get so frustrated about issues like this.

Regards,
Salsaman.