dayplans: blank screen or blank image container after adding an image

[urapadmin]

this comes out of #1151 which got out of hand.

This is where we are: We have two ipads Luiza's and Laurel's which were able to reproduce the one or the other issue reliably until I release test-2 which used a new way of processing the file-identifier-cache during image creation. Instead of opening a flickering overlay window I changed the layout in situ. The side effect was a short but in fact unavoidable tab switch. While this is a bad way of doing it for me it worked reliably on Luiza's ipad but Laurel got a blank screen once (out of several tries).

Pretty devastating.

Now this here is about a third take:

recording 11.5-test-3

• [ ] in the Guinea pig section you still find "dayplan_in_situ", which, if checked solely, still does what 11.5.-test-2 did. That's the mode that failed once on Laurel's ipad. 👉 In this mode the excavating form shows "experimental" in the upper right corner.
• [ ] if you check dayplan_deferred (Please only check one of the options) the processing is not done in situ but with a delay that is supposed to give filemaker time to "settle" (we are back to the time when computing was a rather analog thing you should not do too speedy). You should see one slightly delayed flicker. After that your image should be fine and with the correct identifier in the gallery. 👉 In this mode the excavating form shows "totally experimental" in the upper right corner.

[urapadmin]

iOS 14.7.2

I can do this now too. And here is proof that Filemaker is still alive behind the grey panel.

[urapadmin]

Just for the records, what we want is that it works with nothing checked. DLC is not adding the identifier to the gallery

[urapadmin]

Fun fact: My old mini 4 that never shows any of the error types is on Luiza's problematic 15.0.2 version that seems to have caused all the 2bs. It is such a mess.

[luizaogs]

Yeah I just tried adding a zillion more dayplans with nothing checked and no errors. Wow. If the 2b was truly a version problem you would think I would have thought to update it sooner...

[urapadmin]

okay, I'd say let's split this up now into 2b -> which we will consider solved by a new OS version. and 1 -> which is still there and needs an overhaul of all image containers. For the latter I create a new ticket, for the former we use this here and I close it.

[urapadmin]

new ticket for error type 1: #1249.

I close this and we go with updating the OS to something else than 15.0.2 for type 2b.

2a we have not seen anymore and 3 I ignore for the time being.