Please show your relevant blocks, or upload your aia project here for me to take a look.
....My project is not exactly as you instructed me. I just want to disable the zooms - and + that appear when scrolling up and down the page.
Please upload your aia project, Testehoje, let me see if it works here. If it does, then it may be a device/Android thing.
What device are you testing with, and what Android version is it running ?
(edit - I have also tested on Pixel 8 Android 13, this also works OK for me)
1 Like
I missed that you were using "backpressed" and not initialise.
If you want to use BackPressed to load your site, that is OK, but you must use Screen1.Initialise to setup your webviewer with the extension, this means everything "gets set" before you do anything else.
1 Like
I didn't notice that, sorry... It's ok now. So which blocks should I drag to disable the + and - zoom in on my app?
It should be done without needing any other blocks, as per my documentation, zoom features are turned off by default
1 Like
Update 2.2 release
- Provides Geolocation permissions
- Provides method for camera and microphone permissions in webviewer
Can you add a way for me to download because I can't open the link due to blocks
What is blocking the download link? No issues here
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.
Hi, TIMAI , can you please allow adding custom headers to the extension please? Thanks
There is no way to have it with webviewextra as i am using the native already
You have a niche requirement, use what is available, I do not see the point in replicating it.
The main focus for webviewextra is for uploading and downloading files...
1 Like
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
You could use this version:
uk.co.metricrat.webviewextra2.1release.aix (24.9 KB)
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.
thanks for your reply . i don't need permissions for camera and audio