What is the correct path to read ASD files now?

Of course I checked your APK. I also made a new version of the application based on picasso this way.
Unfortunately, I don’t like the way it works.
This should work fine in kodular. Without extra extension.

@vknow360
As for the picasso component, this
Does not save files in ASD. Only I’m starting to suspect it’s a bug with Kodular.
The transition animation is tricky as I have to load up to two components regularly.
It works. But the way is not right. I don’t like how it works.
Every few dozen photos also hangs while downloading and does not cause an error. So I have no way to react.
I use it continuously and the program stops the image switching animation. When I used another component it was fine so I wrote yours is weak.

Why should Picasso save files in ASD?
It is an image loading extension. You need an image path/URL and a view component, that’s it.

I didn’t understand what you wrote later so post a video of issue.

2 Likes

I just explained what I don’t like and why I don’t want to use it.
It’s nothing personal. The extension itself is great, just not for my application.

That’s your choice but if you are facing any issue then it’s my choice (actually responsibility) to fix that.

3 Likes

I think the thread can be closed.
The bug is fixable in the new Kodular release. Or maybe something broke in my project.
I’m not going to update the application anyway.
Therefore, no further discussion is necessary.

I have already fixed the other applications that are regularly updated in the Play Store and I’m satisfied.

This is what I did:

Image can show the picture, but File.Exists returns false

Maybe try with File manager extensions.

How often has that already been said, especially by me:
“The File component needs a relative path for this.”

:question:

Everything you have written is obscure and incomprehensible. And if you think you have to determine issues with an extension, explain the problems precisely and show your blocks.

Oh, Thanks for this.
Maybe Kodular should make all the component accept the same format of file path.
like //aa.txt for assets, ~/aa.txt for private , #/aa.txt for ASD, /sdcard/aa.txt for sdcard.
of course, it also can accept the full file path.

1 Like

No, because the File component is the only component that can write to the privateDir. Therefore this path (without an initial slash) is only required here. The same goes for the assets. Because this is only required for the File component to differentiate it from the privateDir.

No, everything works. I have already written an explanation. There is no point in writing about it further.

Then, for the sake of clarification, I would like to conclude that there are no problems with the Picasso extension (to my knowledge).

1 Like
  • //test.txt for assets
  • test.txt for privateDir and
  • /test.txt for the root dir of the external storage for Android < 10.
    For Android > 9 this is redirected to the ASD.

So from now we can not set picture component from asd? Cause i got same problem

What i mean is: all the components, not only File, but also Webview, Image, VideoPlayer, and other components need to read/write local files, they should have the same philosophy of file path like File.
take Webview as example, Webview.LoadUrl (//index.html), this should be working, no matter in companion or in Apk.

But this is working. Setting picture from asd.

I use this extension

This what i got

But ur .aia is work . I will try again with extension downloadasd

Now i know what my problem. Its work after i disabled hight quality image

can anyone explain why if it is set to high quality image than set image does not appear?

Edit : now i use image utilities , so even if hight image quality is enabled, the image is still visible

In fact, that was the cause.

So the bug was found. Now just need to fix it