Debugger key bindings (n,s) do not function

[brewer]

With a saved file loaded and the debugger launched, nothing happens when 'n' or 's' is pressed, regardless of which panel has focus. (The exception is the code panel, which accepts the input as a code change.) Debugger behavior is as expected when clicking on the buttons on the Debugger panel. Other key bindings may also have this problem, I did not check.

This is under Strawberry Perl 5.12.3, Win 7 Pro.

[bowtie]

as far as I am aware there are none, at present
just tool-tips

need to look at wxAcceleratorTable, i think, any comments

[bowtie]

am I correct in saying bitmap buttons don't have key board short cuts

if so I will close as not relevant

[brewer]

Would it be more appropriate to recast this as an enhancement, suggesting that the buttons should have keyboard shortcuts?

[bowtie]

brewer,

you can not assign keyboard shortcuts to bitmap buttons as far as I know

if you know otherwise, explane otherwise close this ticket

[szabgab]

Shouldn't these all be "Padre actions" that are bound to the bitmaps and that can also be mapped to the keyboard?
Though this still does not solve the problem of "how to know if 'n' means next or if the user just wanted to type n in the editor?

[brewer]

bowtie,

Thank you for the clarification. I do not know whether keyboard shortcuts can be assigned to bitmap buttons, so if this enhancement is not possible then of course this ticket should stay closed.

szabgab,

Well, I don't know about all "Padre actions", but I would suggest that "Padre debugger actions" that are bound to the bitmaps should be mapped to the keyboard if possible. People (including me) know and love these shortcuts!

This ticket grew from my question in #padre (see ​http://irclog.perlgeek.de/padre/2012-02-10#i_5130504 and the following 90 minutes). I had assumed that the debugger keyboard shortcuts would be available when the debugger pane had focus, and was confused when they were not. (My apologies to both of you for a poorly-worded ticket based on this incorrect assumption.) The behavior I expected is that the keystroke target would follow focus: 'n' would mean next if the debugger pane had focus, but an 'n' would be typed in the editor if the editor pane had focus. This ticket was an attempt to suggest that behavior as an enhancement.