Oh, I see. Yes, I think that's the problem! I see the search/replace commands, but they are applied to specific files, and not to all. And there is the missing rule to remove the "selection" when there are no choices. I'f it helps, I'll see if I can update it (I'm no expert in sed, but I think I can manage), and see if I can get it to compile it and run it with only those sed changes, and without my previous edits
Apparently wxGlade is kind of deprecated and wxCrafter and wxFormBuilder are better. But when I tried them, the imported XRC file was changed on loads of places... So as for the current status of catapult (no active development anymore), I'd rather not touch it, unless strictly necessary.
If it helps, I'll see if I can update it (I'm no expert in sed, but I think I can manage), and see if I can get it to compile it and run it with only those sed changes, and without my previous edits
I think it would, sounds like the most straightforward fix.
Note that the OSD menu was also adjusted in last releases to be more similar to using a real MSX. Please try it.
Very interested about this. Some here don't even use Catapult (or any other) as says the built-in menus are enough. Not sure if for development could fit (un/plugin devices and all that stuff) well or if it has the machine compatibility check that Catapult has, pretty handy. Anyway the machines are only profiles, so they could be shared and copied to openMSX config I think, right?.
I didn't see your questions before, but can you rephrase? I don't understand what you mean. There are no Catapult specific machine profiles.
The check also exists as a script you can start from the console. It is immensely much faster.
