|Viewing Issue Advanced Details|
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06347||Interface||Minor||Always||Aug 12, 2016, 02:49||21 days ago|
|Tester||Tafoid||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||Resolution||Fixed||OS||Windows Vista/7/8 (64-bit)|
|Version||0.176||Fixed in Version||0.184||Build||Normal|
|Summary||06347: LISTXML:: sampleof entries show up on devices which do not have samples|
During the construction of the XML list, the devices are accumulated and placed in the file after the final MAME machine. As the alphabetical list of set names are checked for devices, the first time an instance shows for a device, it is logged and appended to the end of the -listxml output. The problem arising is that if that machine is set up to use samples and has a sample set, all the devices which are discovered from that machine have this sampleof="xxx" portion attached incorrectly to the device.
For instance, 005 - the first machine listed in XML, has 8 devices that show in -listdevice and since each one of them are discovered for the first time being used by a machine, they get added to the device section with the incorrect attribution of having SAMPLES.
<machine name="z80" sourcefile="src/devices/cpu/z80/z80.cpp" isdevice="yes" runnable="no" sampleof="005">
PLEASE NOTE: There are some devices which indeed have samples directly related to them and also list their samples out as you'd expect whereas the above examples do not.
<machine name="nes_jf23" sourcefile="src/devices/bus/nes/jaleco.cpp" isdevice="yes" runnable="no" sampleof="smoepro">
|Steps To Reproduce||
mame -listxml 005 > xmlout.txt
View xmlout.txt and see the how the initial devices all show to be attached to 005's configuration and not the device itself.
|Affected Sets / Systems||LISTXML:|
|There are no notes attached to this issue.|