 |
To quickly summarize from 0001798 what the challenges are: For this to be useful, this can't just be about the pattern editor column itself (hence I changed the title). This feature would have to change the instrument number representation everywhere in the program: Tree view, instrument editor, note properties dialog, find / replace, comments tab. And since the instrument column may also contain plugin indices (for PC events), this would probably also imply that plugin indices need to be hex as well, which would add even more places to this list. |
 |
Sorry for late reply, but does it truly have to be everywhere? Can't it just be in the sections that people are most likely to see? |
|
|
Of course I could do half-arsed solution. But this is something that matters to me: I don't do that. Because in the end a half-arsed solution almost always means this:
There's no such thing as "sections people are most likely to see". Everyone sees something different, and everyone will spot the inconsistency in a different place. There would be questions such as "I want to automate a parameter of plugin 13 but if I enter In the end, the most important thing remains: An instrument number is just an identifier. I can see why you'd want to enter hexadecimal volumes because there really is a difference to that. But where's the difference in decimal instrument identifiers? You could write an XM file in FT2 where after every 10th instrument there are 6 empty instrument slots and you would end up with "decimal-looking" instrument numbers even in FT2. Most of the time you don't even have to enter instrument numbers: You browse your instrument list, pick an instrument and now all numbers are entered automatically next to each note. Whether they show up as "16" or "10" doesn't matter. I see no value in spending hours on implementing something that in this case doesn't even have cosmetic value, as far as I'm concerned. |
|
|
Okay, I understand. |
- Anonymous
