Reply to thread

Message

<blockquote data-quote="Lehmden" data-source="post: 1134466" data-attributes="member: 109222">Hi.In my understanding a &quot;fallback&quot; is an &quot;emergency solution&quot; if nothing else is possible. And for this it only should pop up if there is nothing else that can be displayed.To me it looks like this atm:We need to display a gfx. So we display the fallback and then have a look if there is something different to display. If yes we replace the fallback, if no we do nothing. IMHO it should be like this:We need to display a gfx. So we have a look if there is something to display. If yes, we display it, If no we display the fallback.IMHO this makes more sense. As the &quot;not displayed&quot; GFX is &quot;faster&quot; than the fallback in any case (as it actually is always &quot;there&quot; already) it did not matter if we need another half of a second to load the gfx from disk (or DB in future). Now we first need to load the fallback gfx from disk and then additionally load the &quot;real&quot; gfx from disk. This lasts longer in any case (maybe only some milliseconds but nevertheless) and also leads to this ugly &quot;flicker&quot;. Maybe this is no &quot;bug&quot; but at least an issue that probably could (and should) be solved by code change.</blockquote>

[QUOTE="Lehmden, post: 1134466, member: 109222"] Hi. In my understanding a "fallback" is an "emergency solution" if nothing else is possible. And for this it only should pop up if there is nothing else that can be displayed. To me it looks like this atm: We need to display a gfx. So we display the fallback and then have a look if there is something different to display. If yes we replace the fallback, if no we do nothing. IMHO it should be like this: We need to display a gfx. So we have a look if there is something to display. If yes, we display it, If no we display the fallback. IMHO this makes more sense. As the "not displayed" GFX is "faster" than the fallback in any case (as it actually is always "there" already) it did not matter if we need another half of a second to load the gfx from disk (or DB in future). Now we first need to load the fallback gfx from disk and then additionally load the "real" gfx from disk. This lasts longer in any case (maybe only some milliseconds but nevertheless) and also leads to this ugly "flicker". Maybe this is no "bug" but at least an issue that probably could (and should) be solved by code change. [/QUOTE]

Verification