File path

Discussions related to database technologies, file handling, directories and storage
Ric
Posts: 208
Joined: Tue 17 Apr 2018, 21:03

File path

Post by Ric »

Evening all,
I have got program running in bbcsdl on my laptop which sources images from two folders in @usr$ called 1985 and 2025.
To allow the program to flick between them i use the variable fPath$ which contains the string "1985\" or 2025\" and access them with

OSCLI "DISPLAY """+ @usr$ + fPath$ +"connection.bmp"+""" "+STR$(80)+","+STR$(600-152/2)+","+STR$(480)+","+STR$(304)+","+STR$(1000000)

or similar. This works fine and i had no worries until i tried to put the program on my galaxy tab. All files are copied and are present like on my laptop, but the error "file or path not found" occurs.

Can anyone help

Kind regards Ric
Kind Regards Ric.

6502 back in the day, BB4W 2017 onwards, BBCSDL from 2023
Richard Russell
Posts: 366
Joined: Tue 18 Jun 2024, 09:32

Re: File path

Post by Richard Russell »

Ric wrote: Wed 19 Feb 2025, 17:46 All files are copied and are present like on my laptop, but the error "file or path not found" occurs.
How literally should I take your comment: "i use the variable fPath$ which contains the string "1985\" or 2025\""? If that's really what the strings contain it can never work on any OS except Windows, because you've used a backslash (\) as the directory delimiter rather than a forward slash (oblique stroke: /).

This is what it says in the differences document (section 3.a): "To ensure cross-platform compatibility, a forward-slash (/) should always be used as the directory delimiter, not a backslash (\)". Windows accepts either character, but most OSes don't.

I'd recommend regularly referring back to the differences document so you don't forget any of it.
Ric
Posts: 208
Joined: Tue 17 Apr 2018, 21:03

Re: File path

Post by Ric »

Thanks Richard, it was a case of trying to find a complicated solution and not the one staring me in the face, ho hum.
Kind Regards Ric.

6502 back in the day, BB4W 2017 onwards, BBCSDL from 2023