PureBasic Forums - English

gnozal wrote:

helpy wrote:I copied the new version on my pc (Windows XP SP2 32 bit).
If I call PureFORM.exe an error message is shown
Messagebox titel: Invalid EXE
Messagebox text: is not a valid x86 executable !

You can change the compiler path in Preferences.
You may also modify PureFORM.ini directly : FORM_CompilerPath = C:\YourPBx86path\Compilers\pbcompiler.exe.

Thank you gnozal!

The path was EMPTY!

helpy wrote:

gnozal wrote:

helpy wrote:I copied the new version on my pc (Windows XP SP2 32 bit).
If I call PureFORM.exe an error message is shown
Messagebox titel: Invalid EXE
Messagebox text: is not a valid x86 executable !

You can change the compiler path in Preferences.
You may also modify PureFORM.ini directly : FORM_CompilerPath = C:\YourPBx86path\Compilers\pbcompiler.exe.

Thank you gnozal!

The path was EMPTY!

That was also the case on my machine at home.
I reckon that it doesn't get emptied for you now, with the new version, Helpy ?

Can't wait to check how I will fare at home.

Big "Thank you" to Gnozal if he could fix that.

Captn. Jinguji wrote:Gnozal, I know you are a very nice guy, so I won't answer "...and I can only repeat that..."
Take my word please, I tried your suggestion (several times) already.

Sorry, but I have no other idea ...

Captn. Jinguji wrote:Is it a secret how PureFORM actually arrives at the conclusion that the respective file is " not a valid x86 executable", or could you share the criteria with those of us who are concerned with the problem

PureFORM checks the PE header of the PBCompiler executable (for #IMAGE_DOS_SIGNATURE and #IMAGE_FILE_MACHINE_I386).
If it's valid, it runs the PBCompiler to check the PB version. If not (or if the path is invalid), it sets the compiler path to "".

Captn. Jinguji wrote:... That was also the case on my machine at home.
I reckon that it doesn't get emptied for you now, with the new version, Helpy ?
Can't wait to check how I will fare at home.
Big "Thank you" to Gnozal if he could fix that.

The PE check is the same in the new version.

I now can really say: "A ton of thanks" to you Gnozal.
It's fixed here, too.
Although PureFORM seemed to be working alright each time after I clicked the error message away,
there always remained that uneasy feeling that something else might possibly not be as it should.

Thanks again
CJ

gnozal wrote:If it's valid, it runs the PBCompiler to check the PB version. If not (or if the path is invalid), it sets the compiler path to ""....

Just an idea: instead of setting the path to "", set it to "<INVALIDATED BY PUREFORM>" or something to that effect:
Of course it's only cosmetics for rare cases, but it definitely takes out some irritation once one is forced to dig that deep
into PureFORM's entrails.

Hi.

New user, and still green in PB.
I was wondering if any of the fellow PureForm users is using Es/ExGRID, and if so if he has a working config he can share
to declare those as custom gadgets in PureForm.

It would be of great help to be able to visually place the grid in the form designer (great tool btw).

Thanks.

K1m0n wrote:I was wondering if any of the fellow PureForm users is using Es/ExGRID, and if so if he has a working config he can share to declare those as custom gadgets in PureForm.

Hi,
Have a look at the 'custom gadgets' topic in the help file.
There is an example for eGrid4. Es/ExGRID should not be very different.

gnozal wrote:

K1m0n wrote:I was wondering if any of the fellow PureForm users is using Es/ExGRID, and if so if he has a working config he can share to declare those as custom gadgets in PureForm.

Hi,
Have a look at the 'custom gadgets' topic in the help file.
There is an example for eGrid4. Es/ExGRID should not be very different.

Thanks, I got it somewhat working (at least is compilable).
Now I have to understand a bit the OO interface of ExGRID.
But in the process I think I found a PureForm bug:

At setup -> Configuration -> Custom gadgets -> edit.

At the init code field, among other things I have the entry: IncludePath "C:\PureBasic\ExGrid"
At the code generator, the above is translated as: IncludePath "C:PureBasicExGrid"

The same with Free code, my entry is: myGrid\Destroy()
And it is being translated to source: myGridDestroy()

Am I doing something wrong, or its really a bug?
Slashes are being lost/discarded.
Maybe a slash jocker %\% is needed?

K1m0n wrote:At the init code field, among other things I have the entry: IncludePath "C:\PureBasic\ExGrid"
At the code generator, the above is translated as: IncludePath "C:PureBasicExGrid"

As PureFORM supports escape sequences in 'Init code' and 'Free code', you have to use '\\' : IncludePath "C:\\PureBasic\\ExGrid".

gnozal wrote:

K1m0n wrote:At the init code field, among other things I have the entry: IncludePath "C:\PureBasic\ExGrid"
At the code generator, the above is translated as: IncludePath "C:PureBasicExGrid"

As PureFORM supports escape sequences in 'Init code' and 'Free code', you have to use '\\' : IncludePath "C:\\PureBasic\\ExGrid".

How silly of me
Works as expected now.

Thank you.

If the menu builder is active:
You cannot switch to another window (ie: explorer)

If you click on the file browse button (to add an icon to a menu item):
You can switch to another window
BUT: if you click on a window of PureForm that covers up the file browse window, you cannot get back to it.

jassing wrote:If the menu builder is active:
You cannot switch to another window (ie: explorer)

Yes, by design

jassing wrote:If you click on the file browse button (to add an icon to a menu item):
You can switch to another window
BUT: if you click on a window of PureForm that covers up the file browse window, you cannot get back to it.

Click on menu builder in the task list, or use Alt+TAB and select PureFORM.

Hello Gnozal, hello to all,

i have upgraded from XP to Win 7, because an new notebook.

I use your 1.99 build 414.

First, sometimes your PF chrashed.

Then, i chance the startmode for PF to XP mode (config in Win 7).

It seems, that this will help, i have no more crash.

But i do not chance back to win 7 mode, to test it.

So, i can not say exakt, if this will be the reason (startmode).

Are there any known problems in this config?

Thanks.

Hi,

latest build is 425, but I doubt it would change anything regarding the Windows Se7en crash issue.

PureFORM is not Vista / Se7en savvy, so I recommend to avoid the program files directory (UAC issues).
Beyond the UAC stuff, I don't know what Se7en might not like about PureFORM.

Hi

thank you.

i do not use the windows programm folder, or user files folder.

i use only 7 item long names for all folders and files.

i do not use names with blank parts.