When you have too many blocks spread out over too large a surface area,
the Blocks Editor hits a complexity limit when it tries to generate a blocks.png file for the screen.
There are two main approaches to deal with this:
Start a Google Doc with a Table of Contents explaining your app, with sections for Design, Data, Code, including Downloaded Png images of all Events, Procedures, Globals, and with html cross-links for easy navigation. Such a doc becomes easier to read than a complete blocks image, because you have FIND, Next, PREV, back functionality, and you can add paragraphs of commentary around your code. This is my preferred life saver when doing a very large complex app. If you go this route, try to arrange your blocks geographically in a column matching the order of your Table of Contents, then do periodic Clean Up Blocks to pull them inline. This sometimes lowers the load on the Blocks Editor.
Reduce your block count:
Use parametrized procedures for common code
Use Media text files instead of big clumps of text blocks
Use generic blocks instead of repeating component event blocks
Encode repeating decision patterns into lookup tables loaded from Media csv text files (does your blocks image look like a box of combs?)
You don't need a component for every data instance. Reuse those components.
If you can't fit data into a ListView or List Picker, show a small subset of the data in an Arrangement and slide it across the larger list of data.
Custom is full of extra features that i don't need but i get your point and i guess custom headers can be helpful for many people especially that your extension is regularly updated and also just use the native webview
See release notes (V2.2) in the first post for what is not included.
However, if you want your users to have access to the camera and audio through the webviewer, you need to advise them in advance that they need to accept these permissions on first run of your app, so that these functions will work.
i didnt pick you becase the native webview is to lame and givesthat web touch and is not as matured as CEFs Chromium Embedded Framework (CEF) and is this atleast Capacitor Embedded Browser or Cordova WebView (System WebView)
