Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Old cmpro can filter on driver status only.
With the new scanner (and xpath) you will be able to filter on anything inside the xml ;-)

That's awesome!  I can't wait to try it. Thank you

Old cmpro can filter on driver status only.
With the new scanner (and xpath) you will be able to filter on anything inside the xml ;-)

When you talk about "labeled preliminary" are you refering to driver's status,cocktail or emulation attribute? Or all of them?

<!ATTLIST driver status (good|imperfect|preliminary) #REQUIRED>
<!ATTLIST driver emulation (good|imperfect|preliminary) #REQUIRED>
<!ATTLIST driver cocktail (good|imperfect|preliminary) #IMPLIED>


one possible xpath for the emulation attribute would be
xp://machine[driver[not(@emulation='preliminary')]]

or if you want emulation and status attributes being something else than preliminary, you can use
xp://machine[driver[not(@emulation='preliminary') and not(@status='preliminary')]]

the dependencies (needed parent/bios/devices) get added internally

With the current scanner, I only filter by driver status because I thought it was my only option.  Can I filter by emulation status in the current ver 4.048d?

When you talk about "labeled preliminary" are you refering to driver's status,cocktail or emulation attribute? Or all of them?

<!ATTLIST driver status (good|imperfect|preliminary) #REQUIRED>
<!ATTLIST driver emulation (good|imperfect|preliminary) #REQUIRED>
<!ATTLIST driver cocktail (good|imperfect|preliminary) #IMPLIED>


one possible xpath for the emulation attribute would be
xp://machine[driver[not(@emulation='preliminary')]]

or if you want emulation and status attributes being something else than preliminary, you can use
xp://machine[driver[not(@emulation='preliminary') and not(@status='preliminary')]]

the dependencies (needed parent/bios/devices) get added internally

Hi Jack,
welcome to the forum 

ok....small wip mainly about filters:

one little thing on my to do list was supporting xpath for filtering, so I've added that and it gives you fantastic possibilities to filter on specific things..
The filter input field (or commandline attribute) is used for this. Currently it supports regular expressions for filtering machines on name only (see rebuilder readme.md). Using xpath filterings gives you more power. To use it, you need to prefix the filterstring with "xp:", otherwise it's the regular expression filter and your xpath expression needs to select software, machine or game elements.

So here we go with some examples:

Filtering a -listsoftwarelist output by only taking the Commodore software lists into account:

xp://softwarelist[contains(@description, 'Commodore')]/software

Filtering a -listxml output by selecting machines which have a baddump disk:

xp://machine[disk[@status='baddump']]

Filtering a -listxml output by selecting machines which have preliminary emulation status and Taito as manufacturer:

xp://machine[driver[@emulation='preliminary'] and manufacturer='Taito']


If you are familar with xpath, you already can imagine what you can do here. If not, learn xpath ;-)


Another thing with filtering is that you most likely want the dependencies included automatically. So you want to filter on a clone machine, but you also need the parent/bios/devices files included.
The filtering does that for you now, so if you filter on pacman, it will also include all the dependencies for you.

Attached are some screenshot parts which show some filtering for the examples above, also one showing the dependencies (including showing empty machines, which you already know as a feature).

On a side note I did some work on speed improvements, solving some thread safety things which should also positively affect the rebuilder core. And I found a way for handling the weird things like the samples of battles and homerun in a full merged environment...if you have no idea what I'm talking about, well, ignore me or check cloneof versus sampleof versus fullmerged).


So....tada...till next time

Hi Roman,

Thank you so much for your continued development on the new scanner/rebuilder.  Question, for someone like me that filters out machines labeled "preliminary", how would I go about only keeping machines labeled "imperfect" and "good" while keeping the required parents/clones/bios for the set?

Thank you

An amazing video. Good for future game designer or emulators coder check.
https://www.youtube.com/watch?v=sJFnWZH5FXc

That's quality video. I enjoyed a lot. Thank you.

Can't wait to try it... 

ok....small wip mainly about filters:

one little thing on my to do list was supporting xpath for filtering, so I've added that and it gives you fantastic possibilities to filter on specific things..
The filter input field (or commandline attribute) is used for this. Currently it supports regular expressions for filtering machines on name only (see rebuilder readme.md). Using xpath filterings gives you more power. To use it, you need to prefix the filterstring with "xp:", otherwise it's the regular expression filter and your xpath expression needs to select software, machine or game elements.

So here we go with some examples:

Filtering a -listsoftwarelist output by only taking the Commodore software lists into account:

xp://softwarelist[contains(@description, 'Commodore')]/software

Filtering a -listxml output by selecting machines which have a baddump disk:

xp://machine[disk[@status='baddump']]

Filtering a -listxml output by selecting machines which have preliminary emulation status and Taito as manufacturer:

xp://machine[driver[@emulation='preliminary'] and manufacturer='Taito']


If you are familar with xpath, you already can imagine what you can do here. If not, learn xpath ;-)


Another thing with filtering is that you most likely want the dependencies included automatically. So you want to filter on a clone machine, but you also need the parent/bios/devices files included.
The filtering does that for you now, so if you filter on pacman, it will also include all the dependencies for you.

Attached are some screenshot parts which show some filtering for the examples above, also one showing the dependencies (including showing empty machines, which you already know as a feature).

On a side note I did some work on speed improvements, solving some thread safety things which should also positively affect the rebuilder core. And I found a way for handling the weird things like the samples of battles and homerun in a full merged environment...if you have no idea what I'm talking about, well, ignore me or check cloneof versus sampleof versus fullmerged).


So....tada...till next time

Thank you so much Roman!