That was not quite correct... when you address a class, ALL objects of that type would change. But you can also address a single object-instance, in which case you need to know its variable name (which Qt internally handles through the objectName-property, or QObject::objectName()).

A simple example for this is the "qmc2-oxygen" style-sheet, which is just addressing a specific QLabel instance:


Yeah, that's really a cool feature of Qt !

May this will be helpful too.

With regard to GUI styles / style-sheet combinations, please also see this section in the README.

FYI... since SVN r3672 QMC2 has experimental support for Qt 5 (which is at alpha-stage right now and supposed to be released in June/July this year). The changes weren't too drastic, however, Phonon support is not available in Qt 5 at the moment, so it only works with PHONON=0.

Note that Qt 4 support hasn't changed in any way.

OK, I found the reason for the issue with Phonon in Qt 5 (caused by some "make install" bug in Qt-git) and fixed my Qt 5 installation... QMC2 also builds fine WITH enabled Phonon features in case of Qt 5 .

Here's a screen-shot of QMC2 / Qt 5 (nothing spectacular, but it proves that it's working ):



However, they dropped the QX11EmbedContainer class (and friends), which means there's no embedding on Linux with Qt 5. But there's a sub-project working on this, so it should reappear at some point.

Nice!

That reminds me, I need to move my butt on making MAME's GTK stuff work with GTK 3.

Thanks -- caused me a few headaches, though .

Qt 4 will continue to be supported by QMC2 for at least a year or so, well, at least until all major Linux distributions have Qt 5 in their "portfolio" and the embedder-stuff in Qt 5 / X11 (or, actually XCB now) is sorted out.

I just received a number of updates from our French translator (finally ) and had to sync his changes (to the MAME template) to all the other templates. It's probably all OK, but as it was a rather major change esp. for MAME & MESS on Windows I'd appreciate if someone from the Windows faction could test / confirm that it's all OK. You don't need to test the French translation (which isn't fully complete anyway, ~90% done), but of course you can (well, perhaps) .

I only want to make sure there are no syntax errors and that no options got lost. Please check with Tools -> Clean up -> Check template map from the menu and report any suspicious output. Thanks!

SVN r3684:

• imp: MESS device configurator: sort slot-options alphanumerically, add a separator between 'not used' and available options

Sorting seemed reasonable since some drivers meanwhile have many slot-options... like the C64, for example -- I was searching for the ide64 option when testing Curt's latest additions .