PlanetSquires Forums

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 [2] 3 4

Author Topic: WinFBE 1.4.1 on GitHub (August 3, 2017)  (Read 787 times)

Paul Squires

  • Administrator
  • Master FireFly Member
  • *****
  • Posts: 8088
  • Windows 10
    • PlanetSquires Software
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #15 on: August 02, 2017, 10:11:22 PM »

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.
Logged
Paul Squires
PlanetSquires Software
FireFly Visual Designer, WinFBE Editor

José Roca

  • FireFly3 Registered User
  • Master FireFly Member
  • *
  • Posts: 2726
    • José Roca Software
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #16 on: August 02, 2017, 10:26:13 PM »

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

José Roca

  • FireFly3 Registered User
  • Master FireFly Member
  • *
  • Posts: 2726
    • José Roca Software
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #17 on: August 02, 2017, 10:31:58 PM »

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

Paul Squires

  • Administrator
  • Master FireFly Member
  • *****
  • Posts: 8088
  • Windows 10
    • PlanetSquires Software
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #18 on: August 02, 2017, 10:34:10 PM »

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.
Logged
Paul Squires
PlanetSquires Software
FireFly Visual Designer, WinFBE Editor

Paul Squires

  • Administrator
  • Master FireFly Member
  • *****
  • Posts: 8088
  • Windows 10
    • PlanetSquires Software
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #19 on: August 02, 2017, 10:35:33 PM »

...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.

« Last Edit: August 02, 2017, 10:40:06 PM by TechSupport »
Logged
Paul Squires
PlanetSquires Software
FireFly Visual Designer, WinFBE Editor

José Roca

  • FireFly3 Registered User
  • Master FireFly Member
  • *
  • Posts: 2726
    • José Roca Software
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #20 on: August 02, 2017, 11:10:00 PM »

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

Pierre Bellisle

  • FireFly3 User
  • Junior FireFly Member
  • *
  • Posts: 57
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #21 on: August 02, 2017, 11:43:11 PM »

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

Logged

Pierre Bellisle

  • FireFly3 User
  • Junior FireFly Member
  • *
  • Posts: 57
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #22 on: August 03, 2017, 01:13:02 AM »

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...
« Last Edit: August 03, 2017, 01:20:11 AM by Pierre Bellisle »
Logged

Pierre Bellisle

  • FireFly3 User
  • Junior FireFly Member
  • *
  • Posts: 57
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #23 on: August 03, 2017, 01:43:23 AM »

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...)

« Last Edit: August 03, 2017, 01:55:27 AM by Pierre Bellisle »
Logged

Paul Squires

  • Administrator
  • Master FireFly Member
  • *****
  • Posts: 8088
  • Windows 10
    • PlanetSquires Software
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #24 on: August 03, 2017, 08:17:32 AM »

Thanks Pierre, I am investigating this today.... I have a good idea where the problem may be.
Logged
Paul Squires
PlanetSquires Software
FireFly Visual Designer, WinFBE Editor

Paul Squires

  • Administrator
  • Master FireFly Member
  • *****
  • Posts: 8088
  • Windows 10
    • PlanetSquires Software
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #25 on: August 03, 2017, 11:16:43 AM »

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).
Logged
Paul Squires
PlanetSquires Software
FireFly Visual Designer, WinFBE Editor

Paul Squires

  • Administrator
  • Master FireFly Member
  • *****
  • Posts: 8088
  • Windows 10
    • PlanetSquires Software
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #26 on: August 03, 2017, 04:35:14 PM »

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.
Logged
Paul Squires
PlanetSquires Software
FireFly Visual Designer, WinFBE Editor

Pierre Bellisle

  • FireFly3 User
  • Junior FireFly Member
  • *
  • Posts: 57
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #27 on: August 03, 2017, 05:36:02 PM »

Tested. So far, so good...
Logged

Paul Squires

  • Administrator
  • Master FireFly Member
  • *****
  • Posts: 8088
  • Windows 10
    • PlanetSquires Software
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #28 on: August 03, 2017, 05:39:14 PM »

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.
Logged
Paul Squires
PlanetSquires Software
FireFly Visual Designer, WinFBE Editor

José Roca

  • FireFly3 Registered User
  • Master FireFly Member
  • *
  • Posts: 2726
    • José Roca Software
Re: WinFBE 1.4.0 on GitHub (August 2, 2017)
« Reply #29 on: August 03, 2017, 06:02:26 PM »

Seems to work fine now.
Pages: 1 [2] 3 4