This is pretty easy/simple to implement. A POP file could contain both the loading screen and the actual game. Actually writing and building a custom loading screen might be a bit complicated for others, though (requires custom linker script, can’t use PokittoLib). I’m open to suggestions on how to make this simpler.
I like this idea.
On EEPROM we can store a flag with one of three values:
0 - startup screens disabled
1 - startup screens enabled
2 - skip startup screens but set flag to 1
In the emulator, the default would be 0 to make development faster.
Hmm… I think so. It would render a 565 image on the screen then display a standard progressbar over it somewhere?
Btw, the tool is now online here. I’m still working on it and I don’t know if it’s compatible with the last loader I released (I’ve only been testing with the version I’m working on), so think of it as a not-production-ready preview for feedback and don’t start converting all your bins just yet.
If I drop a png it is added to the screenshot column.
Ideally I’d like to drag and drop the image from the screenshot listbox.
Using chrome 70.0.3538.77 on Win10
Yes it is , but sometimes is better then nothing.
Probably just take a small portion of the screen could give better result.
Anyway is really a minor aspect.
Just give some feedback on the forbidden operation or you’ll get lot of user asking for clarification.
I just uploaded a new release. As far as I know, it’s stable enough for everyday use.
Maybe time to bump the version number to 1.0.0? Can anybody see any bugs or missing critical features?
This would be a change in the PokittoLib and a more elegant solution than trying to detect the emulator, as discussed previously.
Would you like me to implement it and send a PR?
, Image of the correct size works perfectly.
, but sometimes is better then nothing.