WinFBE 1.4.1 on GitHub (August 3, 2017)

[Paul Squires]

I wonder does it happen when the "Run compiled programs using command window" option is set in Compiler Setup? That option generates a batch file during compile so maybe it somehow triggers something in Windows 7.

[José Roca]

I have this option unchecked. Didn't even know that it existed.

[José Roca]

The way to launch Windows Explorer is using ShellExecute. Check your code if you're using this function.

[Paul Squires]

I added it a few days ago for fxm so that runtime error messages could be caught/viewed when compiling and running a program using -exx compiler option. Originally I tried to catch the STDERR output through a pipe but it did not work cleanly because unfortunately the compiler was designed to output error messages to STDOUT.

[Paul Squires]

...yes, I am using ShellExecuteEx in a few places within the code_Compile.inc source file.

I use it to execute the batch file that does the actual compiling and I also use it again in the RunExe function that executes and runs the compiled program.

[José Roca]

Maybe it is failing sometimes and launching Windows Explorer as a side effect.

[Pierre Bellisle]

On my side it append every time I press or click F5.
Win7-pro
Explorer in C:\Users\Pierre\Documents
64bit WinFBE

[Pierre Bellisle]

If I REMout RunEXE( gCompile.OutputFilename, gApp.Projects(idx).ProjectCommandLine)
in modCompile.inc, I got no Explorer nor exe running

Something append to gCompile.OutputFilename...

Now all is fine, no more Explorer and program is executed,
problem is I don't know what I did?
I will restart from unzipping the source...

[Pierre Bellisle]

OK, seems that gCompile.OutputFilename is erased somewhere between
If i Then gCompile.OutputFilename = AfxStrRemove(Left(wszTemp, i), wDQ)
and
RunEXE( gCompile.OutputFilename, gApp.Projects(idx).ProjectCommandLine)

Just after
Function code_Compile( ByVal wID As Long ) As BOOLEAN
I did add
DIM wOutputFilename AS wSTRING * MAX_PATH
as a backup for gCompile.OutputFilename

After
If i Then gCompile.OutputFilename = AfxStrRemove(Left(wszTemp, i), wDQ) 
I did add
IF gCompile.OutputFilename <> "" THEN wOutputFilename = gCompile.OutputFilename

and I did add
gCompile.OutputFilename = wOutputFilename
just before
RunEXE( gCompile.OutputFilename, gApp.Projects(idx).ProjectCommandLine)
and all run fine now.

Not a final solution of course, but this should give you a starting point.

Pierre
(See you tomorrow...)

[Paul Squires]

Thanks Pierre, I am investigating this today.... I have a good idea where the problem may be.

[Paul Squires]

I have changed the compile code back to the way it was before the last upload. These changes should undo the ill effect that you guys are experiencing. I will re-upload to GitHub in a few hours (I need to recompile the 64 bit version but I am only on 32 bit machine until then).

[Paul Squires]

New files and binaries uploaded to GitHub.
The release is numbered 1.4.1

https://github.com/PaulSquires/WinFBE/releases

Hopefully this fixes that issue of invoking Windows Explorer.

[Pierre Bellisle]

Tested. So far, so good...

[Paul Squires]

Thanks Pierre, hopefully no more issues. I was pretty confident I knew the reason for the problem so I think I was able to eliminate the issue. Hopefully Jose has similar good results.

[José Roca]

Seems to work fine now.