Search found 4 matches
- Fri Jul 27, 2012 1:44 pm
- Forum: discbugs
- Topic: COMMAND$ changes current directory to app path
- Replies: 0
- Views: 13939
COMMAND$ changes current directory to app path
I started a new thread because I positively identified the problem - it looks like a bug with the COMMAND$ cmd line argument function. When you specify a cmd line arg, it CHANGES the current directory to the compiled app`s install directory.Someone please do me a favor and compile this and let me kn...
- Mon Jul 23, 2012 6:29 pm
- Forum: General category
- Topic: Uses app path instead of curr path for file.open
- Replies: 3
- Views: 15195
Uses app path instead of curr path for file.open
Moral of the story, always include a fully-pathed filespec (even if you have to recreate it by calling GetCurrentDirectoryA), otherwise FNX Basic defaults to the install directory of your app.
If you fully-path the filespec, it uses that.
If you fully-path the filespec, it uses that.
- Mon Jul 23, 2012 6:17 pm
- Forum: General category
- Topic: Uses app path instead of curr path for file.open
- Replies: 3
- Views: 15195
Uses app path instead of curr path for file.open
After borrowing code from the member writing the mp3 player, I just used kernel32 call to get CurrPath. This will work. But I still think FNX Basic should default file.open to current working path (you can always modify that by leveraging the APPNAME$ FN and using just the path portion). Shouldn`t...
- Mon Jul 23, 2012 4:35 pm
- Forum: General category
- Topic: Uses app path instead of curr path for file.open
- Replies: 3
- Views: 15195
Uses app path instead of curr path for file.open
Running FNXBasic 2.1 apr_2012 and compiling for XP x86 & Win7 x64 - symptom is on both. I admit I`ve only had FNXB a few days since I switched from QB64 (didn`t like the HUGE set of runtime DLLs). I also admit I`m using it for CLI apps, and yea its really suited for Visual-type apps, but I just ...