At least for key events...
I am not sure if it is by design, but it is much more difficult to deal with a list of keywords to see what modifiers (shift, control, etc) are in play. It should be a simple and operation, instead scanning the list for each modifier is necessary.
Calling (gdk-event-key-state event) returns a list of keywords.
Looking at the event structure in the bindings, it looks like the structure correctly marks the field as a gdk-modifier-type. I am not sure how it turns into a list...
At least for key events... I am not sure if it is by design, but it is much more difficult to deal with a list of keywords to see what modifiers (shift, control, etc) are in play. It should be a simple and operation, instead scanning the list for each modifier is necessary.
Calling (gdk-event-key-state event) returns a list of keywords.
Looking at the event structure in the bindings, it looks like the structure correctly marks the field as a gdk-modifier-type. I am not sure how it turns into a list...