DisplayEx NES v6.9.0.0 Delay

I'm sorry this has not been released yet. I have been working on it... but its just being difficult.

I suppose now is a good time to talk about a annoying issue that crops up with these mods. I haven't been able to define it well, so have not been able to give it a real name or term. But I commonly refer to it as something like "The issue that makes no sense".

Why it makes no sense is a bit hard to explain. But it just breaks all logic of problem solving and debugging. Traditionally, this issue crops up with the resource reference to a image used in the settings menu. Specifically, the thumbnail for the default background. It's not the image itself. It's not any of the metadata used for the images resource. No typo or anything. Just... NSO randomly decides that it refuses to go past the loading screen if that info is provided. Even going as far as to not allow workarounds, like completely renaming everything about it, moving its placement, and using a different image.

I have seen the issue crop up here and there since the inception of the DisplayEx mod. But I just have not been able to find a proper explanation and fix or workaround. It just... randomly decides to fix itself after I throw the kitchen sink at it.

The best guess I can come up with is... the UI engine for NSO caches resources in a way, that it does not handle things well when resources are cut back between versions. Meaning... this version reduces the amount of resources by 2. 510, to now 508. Or in DisplayEx's case, 531 to 529. When such a reduction occurs, the first resource thats tried to be added after that (509, that thumbnail)... is deemed a problem by the app enough to refuse to load the app when you try to reference that resource.

If I had to speculate further, its that the resource in question now resides at a groupId index previously occupied by another resource in the cache, and its trying to load that resource instead. But such theories and speculations fall apart often when I consider the workarounds I have tried. So... its more like that it deems everything else as good, than this particular resource as bad.

Generally, as I try various tests to hope and understand the issue... it just suddenly goes away. But thus far has not.

The attached NSOM is what SHOULD work. But in the one test carried out by someone other than me... did not work. The hope is... it will work for someone. I cant figure out any more changes I would need to make. All files have been updated, and combed over 2 times to ensure I didn't miss anything. For the json format files, I even wrote code that will programmatically generate them... then compared the results to ensure they were 100% perfect.

If this works for anyone, I suspect it will be people who have not used DisplayEx for NES before, or have not used the app before at all. Basically, people with no pre-existing cache.