QB64 Phoenix Edition
Changing Compile Options - Printable Version

+- QB64 Phoenix Edition (https://staging.qb64phoenix.com)
+-- Forum: Official Links (https://staging.qb64phoenix.com/forumdisplay.php?fid=16)
+--- Forum: QB64 Phoenix Edition Wiki and Repo (https://staging.qb64phoenix.com/forumdisplay.php?fid=41)
+---- Forum: Repo Discussion (https://staging.qb64phoenix.com/forumdisplay.php?fid=42)
+---- Thread: Changing Compile Options (/showthread.php?tid=1374)

Changing Compile Options - bplus - 01-07-2023

When I changed compile options in QB64 pe 3.4.1 I lost all my recent files!

Was this fixed?

It looks like I have latest release according to this site bottom link for QB64pe

RE: Changing Compile Options - Jack - 01-07-2023

bplus, you mean that you lost the recent files history, right?

RE: Changing Compile Options - bplus - 01-07-2023

(01-07-2023, 04:17 PM)Jack Wrote: bplus, you mean that you lost the recent files history, right?

Yes, I am pretty sure I just changed the compiler option and lost the entire recent files list.

BTW I am still getting strange messages in Title bar of Dialog when I use Save File Dialog.
I think that was reported before?
Update: must of been working with old exe file, can't get it to repeat problem with 3.4.1 code.

RE: Changing Compile Options - bplus - 01-08-2023

Confirmed 4x's today, in particular I X the first line option under compiler options on/off.
I change the option on/off it takes a moment to go back to IDE.
I open something (the recent files list still intact) then run it, it takes a longer time than normal under new option.
Recent files are still intact until I open something else or save a change.

RE: Changing Compile Options - DSMan195276 - 01-08-2023

I think the recent file list might be stored in 
internal/temp
and that folder gets cleared out when you change the compile settings (since basically everything gets cleaned up so that it can be rebuilt with your new settings). Certainly it's an annoying issue, it's definitely fixable. I would make a GitHub issue for it if you can.

RE: Changing Compile Options - bplus - 01-08-2023

Quote:I would make a GitHub issue for it if you can.


I won't, I don't do GitHub. I will quit changing Compiler Options before risking Recent Files.

Perhaps Recent files could be stored in safer place?

RE: Changing Compile Options - mnrvovrfc - 01-08-2023

Some people have to be defended from "oopsie" which is common.

Start fiddling with compiler options and get burned "suddenly". Want those options for only one program. Then load another source code which was on the list which didn't need those options, or better yet, shouldn't have them, and after the program is compiled and run it crashes or hangs. WTF but it ran fine before?

That's why I have never touched "compiler options" with the QB64PE IDE. I don't think it makes a great difference, and those who seriously believe that it helps with tiny performance improvements, do the whole thing in C++ and forget about this product.

I mean, on Linux "qb64pe" executable doesn't need "make -j8" or something like that, which I was told to use by somebody else while I was trying to compile something which begged much more memory than I had available.

A solution is to have multiple QB64PE installations, each one with desired compiler options. Name the main directories to that effect if the user has to. Since you seem to be a pack-rat bplus, this might be worth a try, even if each install is at least 100MB on Windows...

If you're clever enough, create a program which stores certain groups of "recent.bin" and "config.ini" which are recalled by a short word, copied to their expected places before "qb64pe" executable is fired. Something on the command line like:

Code: (Select All)
myqb64pe.exe fastest

But this would be only for opening the IDE, not to create an executable from a terminal which is likely to beg more options such as -o and -x.

RE: Changing Compile Options - bplus - 01-09-2023

Quote:If you're clever enough, create a program which stores certain groups of "recent.bin" and "config.ini" which are recalled by a short word, copied to their expected places before "qb64pe" executable is fired. Something on the command line like:


How bout I just rename the thing before changing compiler? maybe I have to copy to another folder?

I was surprised to see it sitting there separate with a bunch of other stuff not wiped out in same folder.

Seems like this could be fixed very easy! maybe the easiest fix in history of QB64!

RE: Changing Compile Options - SMcNeill - 01-09-2023

(01-09-2023, 12:23 AM)bplus Wrote:
Quote:If you're clever enough, create a program which stores certain groups of "recent.bin" and "config.ini" which are recalled by a short word, copied to their expected places before "qb64pe" executable is fired. Something on the command line like:


How bout I just rename the thing before changing compiler? maybe I have to copy to another folder?

I was surprised to see it sitting there separate with a bunch of other stuff not wiped out in same folder.

Seems like this could be fixed very easy! maybe the easiest fix in history of QB64!

Afraid not.  I hold the honor for that fix, when I had to go in and update the version number from "X.XX.0" to "X.XX.1", so multiple releases didn't show the same version when you clicked ABOUT in the help menu.  

Big Grin

From:

Version$ = "X.XX.0"

To:

Version$ = "X.XX.1"


PHEW!!  That was a hard push to sort out and deal with!!

RE: Changing Compile Options - bplus - 01-09-2023

LOL

OK there is probably a host of those kind of easy fixes. This would be one level up?

I should check my rename theory while I have nothing built up in recent files at moment...

So easy, nothing needs be done by developers?

Update: yep! just made a copy and saved it on desktop.