Hi @Teodor,
Sorry for not responding earlier but it’s one of those weeks!
Note:
It is very possible that I’m misunderstanding how the Design View should work here and called a bug what is just my misplaced expectation. If that’s the case, I apologize and ask you to feel free to reclassify the post.
Wrt your very good points:
By “internal browser” I meant the “preview mode”, the one that renders within Wappler the page that I’m building. It’s the one that is activated by the little “eye” button at the top.
Your point on the two errors is well taken, it is likely that those errors are what cause the issue that I see. These errors are created by server connects in the page. I asked a while back about errors like those and it was explained to me that these server connects expect an authenticated user and thus fail.
Unfortunately, the following is taking place:
-
If the server connect and the page expect an authenticated user to render, I don’t know how to do that in Design mode. If that’s the case, then the Preloader behaves the way I observe.
-
The button that “toggles App Connect mode” has no effect in this page, and maybe it is because the page has the Security Provider Enforcer activated.
-
The design view seems to “execute” the logic of widgets like the preloader and any component that has a condition to show or hide. As a result, I see in Design mode that the preloader clobbers the page while and that objects with a conditional Show disappear
Maybe I should just see that there is a preloader widget somewhere in the page (in case I wanted to click on it to quickly find it in the App Structure) or that there are objects that have conditional view settings. Perhaps, the Design view should have a way of toggling these constraints, because while I design, I may want to see those objects and access them.
My current workaround is to go to the Code view and comment out the lines with the Preloader.
Let me know if this helps,
Alex
