James Teh

Ah, that's interesting. I guess that makes sense, though this raises the concern that now we have multiple different definitions of "time movement commands". For "Move relative to the play...

Also, the need to fix item navigation here has made me realise I'm going to need to completely re-think the way I've coded this. Damn.

> ``` > ### 1. Oh, sorry, I forgot to say that the translation problem appears only when I trigger Undo Action with Ctrl+Z after trigger OSARA: Delete all time...

> 1. When I activate a peak watcher on a track and return to the peak watcher context menu, Level type: and value of Level type is not translated. >...

> 1. When I activate a peak watcher on a track and return to the peak watcher context menu, Level type: and value of Level type is not translated. Oh,...

The action names translatable with Crowdin are for actions built into OSARA's C++ code. Custom actions are defined in REAPER's actions dialog and just chain other actions together. Those are...

That's not really feasible. It would be hard to keep the ids in sync with the key map, etc. I think we'd be better off reimplementing the custom actions in...

In terms of implementation, it wouldn't be too hard to write a framework to define some OSARA actions as a set of REAPER action ids and write a script to...

Implementation notes: For FX, we have to handle this differently for tracks and takes. We can do this using template specialisation: ``` template string FxParams::getTitle() { return ...; } template...

Yeah, I thought you might hit problems there, though I didn't suspect an outright build failure. :) On Windows, you're supposed to use [MapVirtualKeyExW](https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-mapvirtualkeyexw) rather than those VK_OEM codes. That...