Ok. does that entail that ill only be able to the pdf extension on screen1 each time
No, what about trying ...
Im trying. If the file is set on screen 1 to legacy and no settings changed on screen 2 it does the same. Im reqding up and attempting all possible solutions.
1 Like
DefaultFileScope is essentially responsible for which storage permissions are declared in the Manifest. Only if it is set to Legacy, WRITE permission is declared in the Manifest.
I have already mentioned / discussed this issue countless times. Search the forum ...
1 Like
@Ellik_Swart my guess is, you are talking about the file scope of the file component...
however what @Anke is talking about is the default file scope, which can be found in the properties of Screen1
Taifun
1 Like
I have specially posted a screenshot so that there are no misunderstandings.
1 Like
thank you all for the above. now I'm going to go forward and send the generated file to google drive.
1 Like
Hi everyone.
I have this problem with this extension.
The extension prints the screen layout, in this way the printout is different for each device.
If the printing is performed on a table it will be different than the printing of a common device.
How can I do?
ref [mod edit]
1 Like
Have you used the Density block to adapt it to the screen?
1 Like
Yes, but the problem is the size of screen.
I would like the pdf generated to have its own size regardless of the device used.
1 Like
hello can someone help me to use a pdf viewer extension from the url or previously shared drive without the need to download it, since it uses a code that downloads, but I need it to be displayed within the application with webviewer... thanks
See here
last set of blocks that use the google viewer in the webviewer
1 Like
is the extension paid?
No extension, just blocks
1 Like
hey what about items those are found in tinydb. if the size of item is greater than the size of pdf, is it add another page or cut them out?
and what does data stored in the tinydb have to do with creating a pdf from visible components on the screen?
1 Like
Hello,
I have a difficulty with this extension on my Lenovo Zuk Z2 Pro running Android 9 (API 28) : it works fine with my Android 12 second phone but with android 9, using the "without 10" blocks, I get no error message, but:
- the pdf file appears when specifically looking for its name with the system's file explorer of the phone (being in android 9 the file explorer can see all files), and is rightly located in the ASD if I get the file infos,
- the pdf file doesn't appear with the file explorer if I manually navigate to the ASD with the file explorer,
- the AI2 app can read the file with the readpdf component, even if a "file exists ?" test comes back false in the companion and the app,
- a share component can't share the file, with a "not found" error.
It's weird, as if the file was "almost" there but not quite. And in my main app the "with10" blocks work fine and the pdf is written, read and shared.
I made a test aia with only the relevant blocks. Put a word or two in textbox before clicking create pdf and see what happens.
test (1).aia (12.8 KB)
and here are my blocks
Any ideas anyone ?
(edited myself to correct one syntax mistake in the create pdf block. Problem still exists with the blocks corrected and reuploaded)
1 Like
Why not just use the 10 blocks ?
(ensure you have an ASD created)
It should work in just the same way on an Android 9
1 Like
Unless I did a mistake in converting in "10" blocks, it doesn't seem to work ?
get a error message on btnreadpdf with "open failed: ENOENT (No such file or directory)"
and a no such file found error for SharePdf and the file doesn't exist.
and the test.pdf that I could find with a search for its name in the file explorer doesn't appear at all.
So it looks like the "10" blocks and "not10" blocks are more different than just the use of ASD ?
