Home Page Forums MAME QMC2 a few minor bugreports for 0.46 on Mac

Not sure if this is the right place to post these, but here are a few bugs I noticed:

- arcade: the only way to filter the list is export it, the other options will not affect it in any way
- pop-up menus disappear by themselves after a few seconds
- drop down menus are to small, and some labels (especially shortcuts) are truncated
- Cmd-Q does not work, I have to use Cmd-X to close the app

and two feature requests:
- is there a way to show multiple images (eg screenshot + title + flyer) at the same time
- is there a way to move the Game Info box so that it shows at the same time as a game image?

Those are no bugs . But anyway, that's the reason why there are themes (only 2 right now), and one can always add more of them... regarding filtering, yes, that's a works-as-designed thing. And regarding keyboard shortcuts: you can change those for the main GUI and QMC2 Arcade (also from the main GUI).

Also, which pop-up menus are you talking about?

re keyboard shortcuts: the menu on top shows the Cmd-Q shortcut, but it won't work, so maybe just a visualization error
re popup menus: for example, if I right click a game, the popup stays open for a few seconds, then closes by itself
re arcade: the ckeckbox next to "use filtering" made me think that the buttons below work independently...

thanks for the good work!

Hmmm, Qt 4 has certain known issues with Command-keys on the Mac, so probably it's really a bug (not necessarily QMC2's fault, but I have to check...). Anyway, as I don't have a Mac myself it's hard for me to test. Could you check if explicit remapping of the keyboard shortcut(s) in question fixes it?! And which shortcut is shown in the key-sequence scanner when you press Cmd+Q?

Interesting... that's "unexpected" to say the least. As I haven't heard of it before may be there's some local setting at your side interfering? Or can someone else on Mac OS X reproduce this?

Yeah, you can choose between using the full game/machine list or a "filtered" version of it for QMC2 Arcade.

Finally back into business after the shit factory stopped supplying the fan.

My bug is:
I can't select an external drive.
I have an external drive with sdlmame executables and all roms, but I can't select it when trying to setup QMC2.

Does the external drive show up in Finder?

Yes.
I even compiled MAME on it using the Terminal and I can launch MAME without issue from the Terminal.
Better: I used RomVault through Parallels to update the ROMs on this very external drive (something that clrmamepro couldn't do, BTW).

So where's the external drive mounted in the VFS? I'd assume something like "/<volume-name>"... and that should be selectable from within QMC2 provided the UID it's running as has sufficient access permissions.

Also, try enabling "Use native file dialogs" in the setup (GUI section) to see if that fixes it... it could be a problem with Qt's built-in file-dialogs. Native dialogs are the ones that the OS provides.

Yeah, I didn't think of typing the path directly; that did the trick, thank you.

But how can I enable native dialogs if I can't pass the first wizard screen? Maybe some note could be added to the ultimate manual.

Well, if that helps, I could simply use native dialogs on Mac OS X as the default setting in future releases (EDIT: which I've done in SVN now)...

Smart move.
Thanks.

The Cmd-Q sequence is intercepted by the "main" application menu, and never reaches the "window" menu. If I reassign the shortcut, it is intercepted as Ctrl-Q


In fact I am unable to reproduce this consistently, so may be a problem on my side.

AFAICT, the Command key on Mac OS X becomes Ctrl in Qt... so Ctrl+Q *is* Command+Q, and this sequence is mapped to "About Qt" in the default setup of QMC2. The default exit sequence is Ctrl+X, so when Command+X works (as you state in the original post) everything actually works as expected . However, when Command+Q is the common key-sequence for this on Mac OS X I might wanna change this... but that's mostly a matter of taste, and QMC2 is not a "native Mac OS X app" anyway.

Also, all of the re-mappable action key-sequences are "application wide" in QMC2, none of them have "window scope" only. (EDIT: I'm probably going to make an exception of that rule for Ctrl+F in the future in order to allow for a "find" hot-key in the browser).

Not sure I understand what you are saying, but in my case, if I choose Ctrl-Q (by clicking Cmd-Q in the reassingment window) as the app close key sequence, then when I use that sequence the application does not quit since it is intercepted before reaching qmc2. In other words, if I press Cmd-Q, the menu bar at the top of the screen flashes, which means that the sequence was received, but it is then apparently never forwarded to whatever code handles key sequences within qmc2.

Interesting... not sure if I can "fix" that if Command+Q is somehow handled specially on Mac OS X. Can someone else on Mac OS X reproduce this and/or shed some light on it?

Anyway, thanks for info! Try using Command+X then (or whatever) for the time being .

Oh, and just in case you didn't check this... since Command+Q is the default assignment for "About Qt", may be you didn't see the key-sequence duplication warning in the front-end log? I'm sure there is one... key-mapping may not work as expected in this case .

Something like this:

And when I then use this key-sequence, I see the following Qt warning (and the mapped action isn't triggered):

That's expected behavior, however, I could probably auto-disable the "overwritten" hot-key instead of mapping it multiple times. But then again, when you overwrite an already remapped key-sequence with something else the same problem will occur... so the general rule is to clean up your key-mappings manually .

ok, so here is what happens:
- if I press Cmd-Q while setting the shortcut, it is mapped to Ctrl-Q, I get the warning, and pressing Cmd-Q does nothing besides flashing the app menu
- if I press Ctrl-Q, it is mapped to Meta-Q, no warning, and then pressing Ctrl-Q on the keyboard correctly shuts the application.

I can live with pressing Cmd-X

Sure, but the solution to your "problem" simply is to assign something else to the conflicting mapping .

Nope, I tried that. Even if I reassign About Qt to another combination, Cmd-Q will still not "get through".
In fact, if I reset the shortcuts, then press Cmd-Q, I do not get the usual Qt about box. This shortcut is catched somewhere before Qt gets it.

Hmmm, that's likely related to the fact that Cmd+Q has special meaning (close application) in a Mac OS X environment, similar to Alt+F4 in the Windows case (Alt+F4 isn't used by QMC2 itself). The easiest way to fix this would probably be to use Cmd+Q instead of Cmd+X as the default key-sequence for it... I could make the necessary changes in SVN, but someone on Mac OS X needs to test it (EDIT: SVN r6350).