Hello Michael,
> > So I'll take that as a vote for Thorsten's initial
> model that has an
> > Edit->Shortcuts on each Window that has
> shortcuts to modify.
>
> Take it as a vote for Edit -> [thing editor] instead of
> folding this into the
> primary configuration page mechanism.
Agreed.
> As to the question of whether to edit shortcuts globally or
> locally, that's a
> tricky thing to consider. There are a lot of shortcuts that
> happen to be the
> same because they are defined the same way in multiple
> different places. A
> per-editor method of editing would (potentially) allow you
> to have one key to
> hit play in the main window, another in notation, another
> in matrix. It could
> get really confusing, and I'm really not sure how we should
> handle that.
Fortunately QShortcut::context tells us which context the shortcut.
In our case the RG Main Window should allow editing of its Window context and
the Application Context shortcuts. Other windows should only allow editing of
its Window shortcuts (filter out the Application context shortcuts).
You are correct, our current setup has duplicate shortcuts crafted to appear as
global shortcuts. So the situation is not that simple.
We could white list the the common "application-wide" shortcuts and force
changes in the RG Main Windows to propagate the changes to all QSettings. I
guess we would then have to setup a listener for each Window so it can me
notified to update its shortcuts.
> > My thought was being able to pull custom shortcuts
> across several installs
> > or for those who reinstall or upgrade to a newer
> release.
>
> Probably a good thought, actually. Think about the
> guy using this in his
> classroom, for instance. He'd want to set all his
> workstations up the same
> way.
>
> > So the more I think about it, the less appealing it
> looks.
>
> Agreed that it's not appealing at all. Can we split
> the difference and not do
> a pretty GUI for this, but make it possible to copy and
> paste some text file
> in a pretty straightforward way? Probably.
Qt stores these in a .conf file somewhere. I guess a first hack for those that
need to do this could cut and paste what is needed from it.
> A classic Rosegarden philosophy: if you can't get something
> really nice done
> within your time and labor constraints, then something
> crappy is better than
> nothing.
noted.
Sincerely,
Julie S.
------------------------------------------------------------------------------
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
