Opened 10 years ago

Closed 10 years ago

Last modified 7 years ago

#3128 closed enhancement (fixed)

Add key shortcuts to switch between views and trigger Check and Simulate

Reported by: Bernhard Thiele Owned by: Adeel Asghar
Priority: high Milestone: 1.9.4
Component: OMEdit Version: trunk
Keywords: Cc: leo.gall@…

Description

It would be nice for "power" users to have key shortcuts to switch between:

  • "Diagram View" and "Text View"
  • "Modeling view" and "Plotting view"

And shortcuts to trigger the "Check Model" and "Simulate" actions

Besides sensible defaults it would be also good to provide the possibility to the user to change the key combinations

Change History (7)

comment:1 by Bernhard Thiele, 10 years ago

Cc: leo.gall@… added

comment:2 by Adeel Asghar, 10 years ago

Resolution: fixed
Status: newclosed

Done in r24911.

Ctrl+F1/F2/F3 switches between welcome/modeling/plotting perspectives.
Ctrl+1/2/3/4 switches between icon/diagram/text/documentation view.

For now the shortcuts are hard coded but may be in future they can be user defined. More important things to be done now.

I hope the default shortcuts I have chosen are fair enough.

comment:3 by Bernhard Thiele, 10 years ago

Hm. On linux desktops Ctrl+F1/F2/F3 is usually bound to switch between virtual desktops.

What about Alt+W/M/P and redefining the menu shortcut for FMI from Alt+M to Alt+I?

comment:4 by Martin Sjölund, 10 years ago

It's usually ctrl-alt that is bound in Linux, but Ctrl+F1/2/3 is still an odd choice.

comment:5 by Adeel Asghar, 10 years ago

One reason for this ticket was also that Dymola has this shortcut. So to keep things consistent for users i kept the same shortcut as Dymola has.

comment:6 by Dietmar Winkler, 9 years ago

Milestone: Futurepre1.9.4

It doesn't make sense to keep closed ticket in the "Future" milestone that were simply forgotten to assign to the correct milestone in the past.

comment:7 by Martin Sjölund, 7 years ago

Milestone: pre1.9.41.9.4

Removing the pre1.9.4 milestone in favor of 1.9.4.

Note: See TracTickets for help on using tickets.