QB64.org Forum
Active Forums => QB64 Discussion => Topic started by: Richard on July 18, 2021, 01:05:12 am
-
8109b81 and many (or all) earlier builds
WIN 10 x 64 2H21 currently updated
I have mainly only used dev builds for all projects for quite a while and problem I faced is that almost all the time I can not load in a program .bas file if it is located on another drive (it almost always load files from the dev build folder which is OK).
Sometimes, even though I can navigate the IDE File Menu, to the folder on the other drive, it may -
"bounce away from the selected folder" rather than displaying the contents
may display folder contents correctly, but if I select a file in question it may either "bounce away" back up a level to say the root menu of all drives OR it comes with a message saying it cannot find the file (have not got a screenshot yet to show this)
It sometimes does the immediate statement above for files in the dev build own folder
Occasionally it behaves itself and I can load a file from anywhere without issues.
The folders for the dev build and other places for my files are not folder protected.
From as far as I can recall I never had this problem with all stable QB64 releases
and I think it only first started with the current dev builds 1.51 series.
Does any one else have this problem?
Edit: The keyboard Enter key and Touchpad (mouse) buttons do not always behave identically in the above situations.
[ This attachment cannot be displayed inline in 'Print Page' view ]
EDIT
When I try loading a file from the "recent list" in IDE > File > I get the message
[ This attachment cannot be displayed inline in 'Print Page' view ]
EDIT Tried to delete broken links, nothing reported broken, and recent files cannot be found by IDE.
[ This attachment cannot be displayed inline in 'Print Page' view ]
-
@Richard I've not had this issue at all and I run solely on dev builds. If I remember correctly, you're always running your system in a very niche mode like on a RAM drive or such. I've never had file access issues in QB64 unless the file truly does not exist. Your mouse and keyboard behaving strangely is not necessarily because of QB64 either. I would like to see what happens when you move your QB64 to a regular hard drive (as that is the typical installation) and see if the issue persists.
-
@SpriggsySpriggs
Thanks for your interest in this matter.
Yes, I am running dev build via a ram drive.
I will now specially set up on C:\qbd4-dev\ and try same and will inform you either way.
I like the RAM drive (A:\) with size 10GByte because it is much faster and does not wear out the SSD (C:\) because of the TBW (Tera Bytes Written) effect especially with constant re-editing of large QB64 files. And yes, windows itself treats a ram drive somewhat differently to "normal" drives - like for instance no log files.
I am editing the above post by adding another screenshot (to keep them all together for you) - the IDE tells me that all links are OK but it still cannot find the files.
Will try to get back to you ASAP.
-
@SpriggsySpriggs
I have installed dev build on C:\QB64-dev\
As per attached screenshots I was attempting to load a file from C:\QB64\ which is where the stable build (and all my programs for both stable and dev builds) is located.
I was unsuccessful to load a .bas file into QB64 dev build IDE (which in this test is located on the C:\ drive.
You may notice \\ in the screenshots (not my doing ???).
[ This attachment cannot be displayed inline in 'Print Page' view ]
[ This attachment cannot be displayed inline in 'Print Page' view ]
[ This attachment cannot be displayed inline in 'Print Page' view ]
[ This attachment cannot be displayed inline in 'Print Page' view ]
-
@SpriggsySpriggs
Also I just installed Qb64 v1.5 (stable build) onto my RAM drive as
A:\QB64-v1.5\qb64\
and from this RAM drive installation of v1.5 I SUCCESSFULLY loaded a file from another drive C:\QB64\ without issues. Only tried one file to report back to you quickly (ideally I should try hundreds of combinations of things).
So I conclude (initially at least) - the stable build works with RAM drive installations but the dev builds do not (for me anyway).
-
@SpriggsySpriggs
Also tried
qb64_2021-04-25-22-43-38_b6705f2_win-x64.7
dev build installed on RAM drive - and SUCCESSFULLY loaded file from C:\QB64\
Will try to locate other dev builds (I do not have them all) and inform you either way.
-
@SpriggsySpriggs
I tried a number of dev builds further to above - and installed on RAM drive. The THRESHOLD (working / not-working) appears to be
qb64_2021-07-15-04-17-45_f3cd0b0_win-x64.7z WORKING OK on RAM drive
qb64_2021-07-15-06-38-03_c8ff781_win-x64.7z NOT WORKING
I only did a quick test, based on trying to load one file from C:\QB64\ into the respective A:\QB....\QB64\ folder.
I do not have any dev builds between the two listed above to try to narrow it down further.
So in summary, when not working get \\ in IDE File navigation process for path.
Hope the above information is helpful for you.