Idea on how to solve a race problem with the test level function (with the preferred emulator set in the options)

[Dariosky-01]

I noticed that there are some rom hacks that cannot be played through a set emulator, if you enter a level to modify it and then click "try with the emulator". This problem does not concern all .nes files, I do not understand what this depends on, but I think that to avoid this possible error of this type we must give the opportunity to choose between a custom emulator as it now exists as a function or a stardard emulator built-in included with Foundry, this should, instead of working as a normal emulator with a window with many internal options running the whole game by opening the game from the beginning, it should give way to play the level starting directly in the level you are editing.

This would allow, not only to avoid possible errors would not allow to open the custom emulator to try the level I could work at, but it would make me immediately get to what anyone really wants by pressing that button, (ie pressing the dedicated button " test level with the emulator "), immediately enter the level you are editing and play it immediately, without therefore intending to switch from the home screen or the map.

This could be possible by adding a choice in options, in a general potion in the window, which makes a choice between using an external emulator as it works now, or using an internal emulator included with Foundry which would only run the level you work on after choosing the level to modify, without going from the map, or from the presentation to the start of the emulation or between the roads of the map to select the level. Skipping all this would avoid wasting a lot of time during rehearsals.

This emulator should have in the options, by necessity some options, a drop-down menu for choosing how Mario should start the level for the test, whether small, or large, or Mario Fire or more. And then it should have, the key setting, the setting option for full screen emulation, and the setting of the, "game genie", so that the operator can add a code and, once added, be able to choose it with a tip [✓] and delete it [×] (this way of adding, using and removing game genes and I mean how the Jnes emulator handles it)

However, I would like to point out that in the window skin setting, for "dracula" setting the buttons at the top have a black design inside them, this does not easily allow them to be distinguished on a dark window color for all the software, preferably the design inside is white. I mean in the buttons at the top where there is also this "test with the emulator" button.

[TheJoeSmo]

This seems like three issues to me. You want better emulator support, a built in emulator, and a few buttons to be improved in dark mode.

The reason you have to set up everything for each emulator is because each emulator can run with different arguments. We cannot know in advance what those arguments will be. The best we can do is hide it behind an 'advanced feature' where the editor will try to run it using the typical instruction. To start it will only show a select emulator button and Foundry will do the rest. If you are using a weird emulator and need to do a special command you can use the old dialog by using the advance feature.

For having a built in emulator, I think that is fundamentally a good idea from a practical standpoint, but also not pertaining to this issue. If the only reason to have a built in emulator is to save the user a few minutes, I think that isn't enough to warrant a built in emulator.

You can have game genie codes and full screen default already. You just have to set those inside your respective emulator. The editor cannot set those as it varies from emulator to emulator. If we made a built in emulator we could allow those settings, but that is in left field. So unless we add a built in editor in the future your best bet is to learn more about your emulator or get a better emulator.

For the graphic user interface, I recommend that you provide a picture of the interface in question. They are a lot of interfaces, so it helps us figure out what you are discussing. And please elaborate on why this interface needs to be changed. Is it mismatched or hard to read?