Menu
▾
▴
[openMSX-devel] [ openmsx-Feature Requests-882469 ] Default extension options in settings.xml
|
From: SourceForge.net <no...@so...> - 2005-12-07 21:07:46
|
Feature Requests item #882469, was opened at 2004-01-22 23:05 Message generated for change (Comment added) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421864&aid=882469&group_id=38274 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: General/misc Group: None >Status: Closed Priority: 5 Submitted By: Laurens Holst (grauw) Assigned to: Nobody/Anonymous (nobody) Summary: Default extension options in settings.xml Initial Comment: Subject says it all, really... Currently, there is a 'default machine' setting in settings.xml. This makes starting openMSX easier, not having to type -machine, etc. on the commandline. However, such a setting does not exist for extensions. So, in order to make permanent use of a particular extension, I would have to edit the machine's hardwareconfig.xml. I would like to keep the machine definitions intact when adding some custom data though... They describe a particular machine (for example Philips NMS 8250) into every detail, and changing the xml would invalidate that. Besides, I don't think extensions like the MoonSound or IDE interface 'belong' in the machine config, as IRL they are not built-in either. Another thing is, the settings.xml is a lot easier to find than the hardwareconfig.xml's. Also, some extensions I would want to use on all machines by default. Suppose I have am developing a program using the debugdevice, and I want to test it on a variety of machines. I would want to keep the debugdevice permanently enabled. Currently, I either have to edit all machine configs, or have to use the commandline parameter (which is longer to type). Another example is the IDE interface. If I were to use openMSX like I use my MSX right now, I would want to have it always connected. Always typing it on the commandline is a bother, and having it in my machine definition is, I think, not appropriate. One other thing which would be useful to add to the commandline, when this is realized, is a -next option (No Extension), with which extensions set by default (like IDE interface/DOS2) can be disabled. Anyways, that's about it :). ~Grauw ---------------------------------------------------------------------- >Comment By: Manuel Bilderbeek (manuelbi) Date: 2005-12-07 22:07 Message: Logged In: YES user_id=78178 Closed because it's basically also in RFE 788926. See there. ---------------------------------------------------------------------- Comment By: Laurens Holst (grauw) Date: 2004-01-22 23:35 Message: Logged In: YES user_id=798154 Note: the slot number of such an extension can ofcourse be given with a <slot> parameter, but if skipped, you could use a default algorithm to place it. I think something like that already happens when adding extensions using -ext on the commandline. An example algorithm would be to allocate the highest possible slot for extensions (IF they have a ROM, for I/O devices it ofcourse doesn't matter), and enabling slotexpanders when needed. By the way, when specifying a specific slot with a <slot> (or similar) tag, it could auto detect whether a slot expander is needed. So I don't know if there is a need for a special slot expander tag. OTOH, it might be consistent with the way things work on MSX to do so... ~Grauw ---------------------------------------------------------------------- Comment By: Laurens Holst (grauw) Date: 2004-01-22 23:12 Message: Logged In: YES user_id=798154 Gah, duplicate (somewhat) of http://sourceforge.net/tracker/index.php?func=detail&aid=788926&group_id=38274&atid=421864 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421864&aid=882469&group_id=38274 |