Hi Sabine, this point was also « discussed » (no answer) here: http://forum.world.st/gtdebugger-debug-actions-buttons-td4874316.html <http://forum.world.st/gtdebugger-debug-actions-buttons-td4874316.html> Yes, the new buttons are counter-productive and there is even no setting to have them usable … You can still with to the SpecDebugger through settings
> Le 25 mai 2016 à 22:49, Peter Uhnák <i.uh...@gmail.com> a écrit : > > Hi, > > yes, this question was raised before, but there are some disagreements over > how it should be, so it may take some time > http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html > <http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html> > > You can also use a startup script to reassign them, such as this one. > https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformDebugger.st > > <https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformDebugger.st> > But a startup script is a temporary solution. > > On Wed, May 25, 2016 at 9:43 PM, Sabine Manaa <manaa.sab...@gmail.com > <mailto:manaa.sab...@gmail.com>> wrote: > Hi, > > today I moved to Pharo5. It is great to get feedback and solutions for > problems so quickly. It is a pleasure to work with Pharo and to have the > community. I am grateful for having this. > > I have one comment. I don't want to complain, I can use it but I was > wondering about the new position and size of the debugger buttons. > > There is a longer distance now from code text pane to the buttons - I see > this as disadvantage to earlier versions of Pharo from the user experience. > The buttons are a lot of smaller - same disadvantage - both if you use the > mouse. > > Ok, after seeing that, I thought "Sabine, you should use keyboard shortcuts > here, too" (I use much of them but interesting - til now not in the > debugger). > > Then I saw the shortcuts for > Proceed cmd+r > Restart cmd-shift-a > Into cmd-e > over cmd-shift-o > through cmd-shift-t > > especially into, over and through have so different key combinations, two > with shift, one without shift. When I debug, I often use for example > into-into-over-over-over-throuhg-through--into-into etc...and with the > combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be > better to have all those shortcuts with or all shortcuts without shift. And > the letters not so far away at the keyboard (e-o-t) > > This is only my opinion and my first impression after one day with Pharo5. I > am sure, after a few days, I forgot that this was uncomfortable because I > have the shortcuts coming automatically into my fingers. > > Regards > Sabine > > > > > > > -- > View this message in context: > http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html > <http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >
