MNotepad in Reaper 4.31

[taji]

Running MNotepad x64 version 7.05 in Reaper x64 version 4.31.

I've run into two issues:

1. Using my pc's keyboard, when I start typing in the text editing area, the letters appear as expected, but when I hit the spacebar, Reaper's transport begins playing back and the space does not appear in the text editing area. The transport is mapped to the spacebar, but I would expect that MNotepad would have a way of intercepting it if the focus is on MNotepad's text editing area. Schwa's Notepad plugin does not have this issue:

http://forum.cockos.com/showthread.php?t=11168

Reaper's default keyboard mapping makes use of a LOT of alphanumeric and punctuation keys so remapping every thing to not use these keys so that MNotepad can process them in the text editor is not really going to work.

2. When typing into the text editor with my PC keyboard, regardless of which radio button I choose (Auto Caps|Caps Lock|Disabled) or whether or not I have my Caps Lock button on my keyboard enabled or not, all of the letters in the text editing area always appear as CAPS. The only time I get lowercase letters is if I click on the built in keyboard and have the radio button set to either Auto Caps or Disabled.

I've tried several vst notepad plugins and everyone of them has some flaw that makes them unuseable. Schwa's is nice but is x86 and doesn't seem to work well in an x64 environment.

MNotepad looks promising. If you fix these issues you'll own the the x64 VST Notepad market.

Thanks,

Taji

[MeldaProduction]

Hi Taji,

well, I'm afraid this is more for Reaper forum. It does work in most hosts. If Reaper chooses to ignore the standard behaviour and override it somehow, we cannot do much about it. It could be hacked of course, but honestly, this is not gonna happen - every hack is a potential problem. For example, in most hosts people were complaining about overriding spacebar, you want the opposite... etc. It's really way more complicated. And according to the forum Schwa is related to Cockos, so... Anyway I suggest contacting Reaper about it. Unlike Mac OS X, where the system design is so stupid, that this just cannot be done, on Windows it is pretty easy to let the plugin process the keys it wants and use the rest, so the behaviour you want can be provided, on the host side however. At least that's my personal experience .

[Impulslogik]

Hi Taji,

well, I'm afraid this is more for Reaper forum. It does work in most hosts. If Reaper chooses to ignore the standard behaviour and override it somehow, we cannot do much about it. It could be hacked of course, but honestly, this is not gonna happen - every hack is a potential problem. For example, in most hosts people were complaining about overriding spacebar, you want the opposite... etc. It's really way more complicated. And according to the forum Schwa is related to Cockos, so... Anyway I suggest contacting Reaper about it. Unlike Mac OS X, where the system design is so stupid, that this just cannot be done, on Windows it is pretty easy to let the plugin process the keys it wants and use the rest, so the behaviour you want can be provided, on the host side however. At least that's my personal experience .

Same here...but you can run MNotepad as a "Separate process". Right click on VST/VSTi => Run as => Separate process...then you have to click on the keyboard symbol on the right side of the text window.

[taji]

Same here...but you can run MNotepad as a "Separate process". Right click on VST/VSTi => Run as => Separate process...then you have to click on the keyboard symbol on the right side of the text window.

That did the trick. Spacebar and caps lock are working. One thing to note, to get the editor to work properly in this mode, you need to click on the little keyboard icon inside the editing area on the right side.

Cool.

Thanks.

[taji]

Same here...but you can run MNotepad as a "Separate process". Right click on VST/VSTi => Run as => Separate process...then you have to click on the keyboard symbol on the right side of the text window.

Oops, should have read your whole response.