"MIDI Editor" Main_OnCommand() ?

Padre_PC · 10-09-2009, 09:03 AM

I've been using Main_OnCommand() to run actions in the "Main" Section, but how do I run actions in other sections? I'm especially interested in the "MIDI Editor" section. I've assigned command IDs but even if the MIDI Editor window has focus they still run "Main" actions. I know there's an "int flags" parameter but I couldn't find documentation anywhere.

Xenakios · 10-09-2009, 09:13 AM

Quote:

Originally Posted by Padre_PC

I've been using Main_OnCommand() to run actions in the "Main" Section, but how do I run actions in other sections? I'm especially interested in the "MIDI Editor" section. I've assigned command IDs but even if the MIDI Editor window has focus they still run "Main" actions. I know there's an "int flags" parameter but I couldn't find documentation anywhere.

A hack solution that might or might not work : find the HWND of the MIDI editor window you are interested in and do a SendMessage() win32 API call to it with the WM_COMMAND message.

schwa · 10-09-2009, 09:14 AM

You should be able to pass the command as a regular Windows WM_COMMAND message to the MIDI editor window.

... which isn't a hack

the commands are designed to be used that way.

Padre_PC · 10-09-2009, 10:32 AM

Thanks, I've tried with FindWindow() then SendMessage(WM_COMMAND) and it works!

However... it worked because I knew the name of the window. It's gonna be hell if I want to make it automatic. Instead of using names I could look for the window which has focus but it would be dangerous since some "MIDI Editor" command IDs are also active in the "Main" window.

Padre_PC · 10-09-2009, 01:20 PM

I think I can get away with EnumWindows() and an "MIDI take:" wildcard search, I'll try that out...

schwa · 10-09-2009, 01:24 PM

The window class will be REAPERmidieditorwnd...

Padre_PC · 10-09-2009, 11:21 PM

Even better then:

void MIDI_OnCommand(int command, int flags)
{
HWND midiHwnd = FindWindow("REAPERmidieditorwnd", NULL);
if(midiHwnd)
SendMessage(midiHwnd, WM_COMMAND, command, flags);
}

Jeffos · 10-19-2009, 03:16 AM

If it exists, I'd like to know the class name of the track routing windows (I need that to prevent a crash described here: http://forum.cockos.com/showpost.php...2&postcount=15)

Jeffos · 10-20-2009, 12:05 AM

ok, I tried:
REAPERroutingwnd
REAPERiownd
REAPERroutingdlg
REAPERiodlg
REAPERgimmesomefunk
REAPERgimmesomejazz
REAPERgimmesomemetal

... none is working. Any clue ? Do I really have to build all possible names (annoying: I also need to retreive "Controls for track x" dlgs) ?

Fabian · 10-20-2009, 12:57 AM

Quote:

Originally Posted by Jeffos

If it exists, I'd like to know the class name of the track routing windows (I need that to prevent a crash described here: http://forum.cockos.com/showpost.php...2&postcount=15)

Can this help?
http://support.microsoft.com/kb/112649
http://geekswithblogs.net/rupreet/ar.../17/57204.aspx

Padre_PC · 10-20-2009, 04:53 AM

Found this:

http://msdn.microsoft.com/en-us/magazine/cc163617.aspx

Fergo · 10-20-2009, 05:13 AM

There's a program called WindowHack which can help you a lot when dealing with Win32 GUI programming. You can get a lot of information from any window in the screen, like classname, handle, child windows, parent, send messages, etc. I really recommend it, even for testing purposes.

Example:

It can also grab windows like the VU Meter, TCP, etc.

You can get it here:
http://www.geocities.com/asmsoft3264/download.html#wh

Regards,
Fergo

Jeffos · 10-20-2009, 05:56 AM

Hey, thanks to all!
Fabian's links talk about spy++ that I don't have here (express edition), but it put me in the good direction => I also found a little comparable tool: http://www.dennisbabkin.com/php/download.php?what=WinID, works fine.
I'll also look to the others tools Fergo & Padre has posted in the meantime, thanks again!

[EDIT] I tried WindowHack: yes, its global "hierarchical view" of parent and child windows is great. However, it's unable to grab info on dialogs such as the routing ones: these dialogs disappear since WindowHack gets the focus... For the record, the WinID tool can do it.

about the pb itself [EDIT2], which is: "how do I know that a routing/control window is opened ?"[/EDIT2] as I was guessing, "Routing" and "Controls" windows are in fact dialog boxes, so I suppose there's no clean way to get them, i.e. I can only get them by name, full name (meaning that I have to build all possible titles), right ?