why if an image is on the internal drive, it is displayed correctly when you point the path to it when viewing it
but if it’s on an external drive, it shows up empty.
Hard to say without seeing the system and the data passed. But two possibilities:
- It is not the full posix path being passed (e.g. the correct volume may have been omitted)
- Tinderbox does not have OS permission for it’s internal WebKit preview to access data on other volumes and an adjustment to System Settings may be needed (if so, I’m not sure which exact setting)
I’m not certain but this are potential user-controlled limits you can try to check before assuming a fault further within the app.
If an HTML page exported, and which uses an image on a secondary volume, e.g. an extra mounted external drive, if ta web browser can run the page and see the image but Tinderbox preview can’t, I’d be looking at security. If the browser also fails to show the image, I’d check the path in the HTML code is correct. But, that doesn’t mean it might not be something else entirely.
HTH 
Yes, the browser shows such a link, from the link from inside the application everything opens normally and without errors, it seems to be banned only for viewing.
I’ve made the application permissions for access to the disc and universal access.
1 Like