Dear Tomasz Grysztar, hi again. I would like to suggest you an another improvement. Can you make FASMW to be able to assign first file to compiler automatically when I start my project from command line? for example string:

would open FASMW editor with according source code tabs and make "YourSource.asm" (first source file in list) assigned to compiler.

Or add some special key to mark one of files in list that I want to be assigned.

Since I was cleaning up this code anyway, I tried adding some experimental modifiers for command line arguments. If you precede file with "+", it is going to be come assigned, and "-" opens the file as read-only (you can also combine both). Please try the interface version 0.99.07.

Thank you very much for all.

While we’re on the topic, I’d suggest to discuss another tweak to the feature. I do not insist but from my perspective it looks quite a valid extension of the feature.

Consider the case when someone downloads FASM and sets up Windows to open .asm files with FASMW by choosing the program to open such files with appropriate dialog. Now the command line used to start FASMW contains plain path to .asm file without any +/– characters. But opening yet another .asm file starts a new instance of FASMW. I guess, it’s valid to assume that having exactly one file in parameters user would expect it to become assigned, at least in most cases.

Still, it’s possible to achieve the behaviour by just modifying default command line for .asm files, so just a suggestion to discuss.

That depends on the value of "OneInstanceOnly" setting.

I have made another update (0.99.08), adding some options to GUI that were previously only available through manual edit of FASMW.INI - including the "One instance only" option. This should make it more visible (previously the only information about it was buried deep within the FASM.PDF). And the same goes for the include path - I really don't know why I had never put it into compiler options before. Perhaps because we are still stuck at "0" version.