Use referenced filename images in Android
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Use referenced filename images in Android
I'm using referenced images files on my project. All works well in iOS, unfortunately under Android the images are not displayed.
Maybe could be a problem I have in the Standalone Settings, any advice will be greatly welcomed!
Maybe could be a problem I have in the Standalone Settings, any advice will be greatly welcomed!
Re: Use referenced filename images in Android
Nobody uses referenced files in image objects? This will be the main mode of using images in LiveCode 6.5 which has resolution independence...
-
- VIP Livecode Opensource Backer
- Posts: 7266
- Joined: Sat Apr 08, 2006 8:31 pm
- Location: Minneapolis MN
- Contact:
Re: Use referenced filename images in Android
The most likely cause is that the referenced file path is wrong. Check your images to see what paths are being referenced. If they are absolute references (i.e., they include the name of your hard drive or user folder) then they will fail if the stack isn't on your own hard drive.
Also check the Files & Memory pane in LiveCode preferences and make sure that absolute file paths are not selected. If it is, then all the images you referenced will be absolute.
Also check the Files & Memory pane in LiveCode preferences and make sure that absolute file paths are not selected. If it is, then all the images you referenced will be absolute.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Re: Use referenced filename images in Android
Thank you so much Jacque!
-
- Posts: 73
- Joined: Mon Nov 12, 2012 4:13 pm
Re: Use referenced filename images in Android
Also make sure that the referenced filename is case-sensitive (only Android?). This is a problem we found with porting from iOS to Android.
Re: Use referenced filename images in Android
Thank you, I will double-check this values.
Re: Use referenced filename images in Android
OK, it was a bug, solved on 6.1.3 rc1. Thank you to all.
Re: Use referenced filename images in Android
hi
i search over all android forum but i don't understand how make visible referenced images in androip app with standalone builder. I'using use livecode 6.5.1
I created only a stack and then add image from File Menù -> New Referenced Control, then i choose icona.jpg from /Users/michix/Documents/LiveCodeFiles. There is no script in stack code; you can see all settings in attachment, but i don't understand where i have to specify specialFolderPath
i search over all android forum but i don't understand how make visible referenced images in androip app with standalone builder. I'using use livecode 6.5.1
I created only a stack and then add image from File Menù -> New Referenced Control, then i choose icona.jpg from /Users/michix/Documents/LiveCodeFiles. There is no script in stack code; you can see all settings in attachment, but i don't understand where i have to specify specialFolderPath
Re: Use referenced filename images in Android
Hi michix74,
1. welcome to the forum!
2. The trick is to use RELATIVE (to the stack) pathames (filenames) and
not absolute pathnames to make it work without scripting!
Do this:
1. put all your images you want to reference in your app into the same folder as the stack (the later APP)
Or use a substack "images" or whatever.
In my example I presume that the image is in the same folder as the stack, no subfolder!
And I will use an imaginary image named "trasonos.png" (I just made up that name!
)
2. Then do NOT use the menu to create a referenced image but use the image tool to create an empty image object.
3. Open the inspector palette for that image and enter the filename manually in the "filename" field in the inspector!
This means JUST the filename
traonos.jpg
NO folder or anything else!
Since the eingine will look into the same folder as the stack for images it will find it, since you entered
the correct relative (to the stack) path! OK, it is not really a path but a filename, but you get the picture
)
If you have a subfolder named "images" enter:
images/trasonons.jpg
4. The image should appear in the image object.
5. Congratulation, you just created your first referenced image with a relative path!
6. Now add the image(s) via the "Copy files..." tab in the standalone builder like before and it will work on your device!
And on any other machine be it a tablet, smartphone or desktop machine!
Now if you want to access that image on the devide in any script (just an example, you dont need to
) here is where
the standalone builder will copy it to:
specialfolderpath("engine") & "/trasonos.jpg"
Look Ma, no scripting
Best
Klaus
1. welcome to the forum!
![Very Happy :D](./images/smilies/icon_biggrin.gif)
2. The trick is to use RELATIVE (to the stack) pathames (filenames) and
not absolute pathnames to make it work without scripting!
Do this:
1. put all your images you want to reference in your app into the same folder as the stack (the later APP)
Or use a substack "images" or whatever.
In my example I presume that the image is in the same folder as the stack, no subfolder!
And I will use an imaginary image named "trasonos.png" (I just made up that name!
![Very Happy :D](./images/smilies/icon_biggrin.gif)
2. Then do NOT use the menu to create a referenced image but use the image tool to create an empty image object.
3. Open the inspector palette for that image and enter the filename manually in the "filename" field in the inspector!
This means JUST the filename
traonos.jpg
NO folder or anything else!
Since the eingine will look into the same folder as the stack for images it will find it, since you entered
the correct relative (to the stack) path! OK, it is not really a path but a filename, but you get the picture
![Very Happy :D](./images/smilies/icon_biggrin.gif)
If you have a subfolder named "images" enter:
images/trasonons.jpg
4. The image should appear in the image object.
5. Congratulation, you just created your first referenced image with a relative path!
6. Now add the image(s) via the "Copy files..." tab in the standalone builder like before and it will work on your device!
And on any other machine be it a tablet, smartphone or desktop machine!
Now if you want to access that image on the devide in any script (just an example, you dont need to
![Cool 8)](./images/smilies/icon_cool.gif)
the standalone builder will copy it to:
specialfolderpath("engine") & "/trasonos.jpg"
Look Ma, no scripting
![Very Happy :D](./images/smilies/icon_biggrin.gif)
Best
Klaus
Re: Use referenced filename images in Android
thank you so machKlaus wrote:Hi michix74,
1. welcome to the forum!![]()
2. The trick is to use RELATIVE (to the stack) pathames (filenames) and
not absolute pathnames to make it work without scripting!
Do this:
1. put all your images you want to reference in your app into the same folder as the stack (the later APP)
Or use a substack "images" or whatever.
In my example I presume that the image is in the same folder as the stack, no subfolder!
And I will use an imaginary image named "trasonos.png" (I just made up that name!)
2. Then do NOT use the menu to create a referenced image but use the image tool to create an empty image object.
3. Open the inspector palette for that image and enter the filename manually in the "filename" field in the inspector!
This means JUST the filename
traonos.jpg
NO folder or anything else!
Since the eingine will look into the same folder as the stack for images it will find it, since you entered
the correct relative (to the stack) path! OK, it is not really a path but a filename, but you get the picture)
If you have a subfolder named "images" enter:
images/trasonons.jpg
4. The image should appear in the image object.
5. Congratulation, you just created your first referenced image with a relative path!
6. Now add the image(s) via the "Copy files..." tab in the standalone builder like before and it will work on your device!
And on any other machine be it a tablet, smartphone or desktop machine!
Now if you want to access that image on the devide in any script (just an example, you dont need to) here is where
the standalone builder will copy it to:
specialfolderpath("engine") & "/trasonos.jpg"
Look Ma, no scripting![]()
Best
Klaus
it's really work and now, in copy file, i have only non-abosute path to file