...well, 3 actually:
1a) the "quicksearch" field on the module load screen could be emptied when the cursor switches between file, directory, etc. (user presses tab or left/right) This way i won't always end up searching for directories named "wipwip" or "sampsampsamp" :)
1b) a similar feature on the sample/inst load screens (f3/f4, enter) - maybe just react to 1 letter and go to that position in the list?
2) on the pattern editor, map "#" on the volume column to toggle between volume/panning - so that non-US keymap users can FINALLY stop switching their keyboard to US each time they want to enter a panning command :D This is similar to the === note-off entry that was taken care of several months ago - on many keyboard layouts, including canadian french and spanish, the key under ESC does # - i'd be happy to use the accent key followed by space (which normally outputs a character) but it doesn't do anything.
oops, i just learned that stuff between backquotes gets put in monospace font :D
1a) ITEXE didn't do this. Does anyone else want to weigh in on it?
1b.1) Done. Expect it in a build later today.
1b.2) No. That would conflict with keyjamming.
2) No. That conflicts with Shift+chord entry. Does your non-US keyboard really have no backtick or tilde key?
1a. Slightly annoying but I sometimes take advantage of it. If my search box got erased every time I switched widgets that would be annoying too. I wonder if there is a middle ground between the two, but I can't come up with anything off the top of my head. I'll try to pay attention to how I use it and maybe I can figure a use pattern out that might lead itself to an obvious behavior.
1a) other suggestion: position the cursor in the other field (file/directory) as though the quicksearch had just been typed on it, rather than the top of the list.
1b) got it :)
2) i don't get it.... # doesn't do anything on the volume column.... maybe a feature i never use(d)...? Mapping # to === (note off) on the note column was very, very useful.
On most keyboard mappings with accents (such as cf and spanish) the backtick is a "dead key" - which means pressing it doesn't actually type anything until you press another key, usually the vowel on which you want the accent (in this case, è à ò etc.) To type just a ` you'd press the ` key followed by space, but that doesn't do anything in schism's pattern editor.
# is shift-3 on a US-keyboard. It doesn't map to note-off; where is the # on your keyboard?
>>642
It's the key below escape on a French layout I think.
How hard would it be to modify schism's input layer to use the IT keymaps?
On canadian french keyboard, # is just under escape, which makes # == note-off very, very useful. Shift+3 is slash. Above mentioned ` "deadkey" is between ;: and enter.
For some reason Schism doesn't react to deadkey presses, or deadkeys followed by space which outputs the actual ` or ^ or whatever in, say, a text editor or xterm.
> How hard would it be to modify schism's input layer to
> use the IT keymaps?
iirc those had to be compiled with an assembler, right? (that was weird!)
Well, that's because they were essentially just asm code. I don't imagine it'd be too difficult to parse them though.
(Wait, your backtick key is where apostrophe usually is? That explains all the weirdos who use backtick instead of apostrophe! suddenly everything makes sense
Ah. That's because of the magic scancode translator!
I've added it to the pattern editor when checking for backticks. Let me know if it solves your problem.
> For some reason Schism doesn't react to deadkey presses, or deadkeys followed by space which outputs the actual ` or ^ or whatever in, say, a text editor or xterm.
If it doesn't on the message editor page, it likely never will. SDL is blissfully ignorant about a great many things.
> How hard would it be to modify schism's input layer to use the IT keymaps?
Not hard, but also not as useful as you might think...
Fixed. Thanks!
Seb: what keymap do you use?
>>649
US.
Also here's some extra closing punctuation to make up for that last post.
...)
> 1b.2) No. That would conflict with keyjamming.
oops DUH, kinda stupid of me that i didn't think about that.... which reminds me, when comes keyjamming on the instrument load page? =) =)
(somehow the word "keyjam" always reminds me of those good old mortal kombat games me & my brother used to play on the same keyboard, heh heh)
> 2) No. That conflicts with Shift+chord entry.
I still don't know what is shift+chord entry.... is it something related to template mode?
I always kinda preferred FT2's term, "keyjazz".
> which reminds me, when comes keyjamming on the instrument load page?
It's not a huge priority, but it could be done- simply double MAX_SAMPLES and load the temporary (fake slot) instruments' samples into the upper-half of the sample set.
> I still don't know what is shift+chord entry.... is it something related to template mode?
On F2, hold shift and type QET (C, E, G), then release shift.
Ah! Interesting. That explains why sometimes notes would end up in weird places when I'm doing a lot of note input at once.
However it kills the selection area. Any way to get it not to do that? (Same thing goes for shift-tilde for fadeoff, but I never worried too much about that as it's not a very prominently used key)
Ah, nice feature, even impulse tracker had it and i never noticed! I used to always set the cursor stepping to zero to get similar effect.
Yeah, it selects the chord you just typed, same as shift+whatever movement (which could be useful in this case) - however it.exe doesn't select the chord.
Done. Expect this to be in the next build.
I also included a reimplementation of an impulse tracker bug for fun (only available in classic mode)
> Done. Expect this to be in the next build.
uh, now it's behaving a bit weird: the first chord i enter gets entered correctly, but then if i enter other chords, it skips between channels in a weird way. Same notes get put on the same channels, and different notes get put on channels at the right of the chords (kinda weird to describe)