View Issue Details

IDProjectCategoryView StatusLast Update
0000455OpenMPTGeneralpublic2013-12-17 13:57
ReporterDiamond Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Platformx86OSWindowsOS Version7
Product VersionOpenMPT 1.22.07.* (old testing) 
Summary0000455: Illogical key conflict in different contexts
Description

I have [ and ] assigned to "Previous/Next Instrument" in the "Global Keys" section. I tried to assign these same keys to "Previous/Next Plugin Preset" in the "Plugin Editor" section. However, I receive a conflict warning and although it allows the assignments anyway, the keys do not work in the plugin editor. I can't see any reason why these assignments should conflict and the keys wouldn't work in the plugin editor. Is this a bug or am I missing something?

TagsNo tags attached.
Has the bug occurred in previous versions?Yes
Tested code revision (in case you know it)

Activities

Saga Musix

Saga Musix

2013-12-17 13:38

administrator   ~0001407

I can't see any reason why these assignments should conflict

Because they are both part of the same hierarchy. If they were in two different contexts that don't share a hierarchy (e.g. sample and instrument editor), you wouldn't get a warning.
Anyway, global shortcuts are, as their name suggests, global, so they work in any situation. Just have a look at the pattern/sample/instrument editor while the plugin window is open and you will see that your shortcut will indeed change the current instrument.

Diamond

Diamond

2013-12-17 13:55

reporter   ~0001408

I see. I had a suspicion this might be the case, but I believe the times I have tested this from the VST editor I was in the "General" tab so of course it didn't change the instrument. Sorry for wasting time with this issue. I should have tested more thoroughly before posting.

Saga Musix

Saga Musix

2013-12-17 13:57

administrator   ~0001410

No worries. The keyboard stuff is far from being the easiest to understand part in OpenMPT (both the UI, functionality and the code behind it :).

Issue History

Date Modified Username Field Change
2013-12-17 06:11 Diamond New Issue
2013-12-17 13:38 Saga Musix Note Added: 0001407
2013-12-17 13:55 Diamond Note Added: 0001408
2013-12-17 13:57 Saga Musix Note Added: 0001410
2013-12-17 13:57 Saga Musix Status new => closed
2013-12-17 13:57 Saga Musix Resolution open => no change required