PureBasic Forums - English

What happens if you rename the Help file so it can't be found?

MachineCode wrote:What happens if you rename the Help file so it can't be found?

it loads my browser, 3 times with
http://gnozal.ucoz.com/PureFORM/PureFORM_Manual.htm

browser then has focus, I switch back to pureform and again, it loads up 3 more browser pages.....

Did you install some software / tool that may mess around with shortcuts ?

PureFORM starts the help if (GetAsyncKeyState_(#VK_F1) & 32768) is true.

I am using build 419 and having trouble with the Code Infuser. I keeps getting corrupted somehow. Seems very touchy.
Overall, though PureFORM is cool. I'm just having a bump in the road here.

DB

purebuilt wrote:I am using build 419

That's odd ; latest public build is 417 iirc.

purebuilt wrote:and having trouble with the Code Infuser. I keeps getting corrupted somehow.

If you could post the steps to reproduce the issue, I would take a look.

Sorry, build 417.

The issue I believe happened when I had set a code infusion and then changed a menu constant. It seems to not check if a device handle exists before trying to write to it. Once I deleted all the code infusion elements I was able to put them back for everything but the menu (which I am still developing). They are working but I have not added any menu items code infusions back. I love the tool though and the code infusion idea is great. I wish PB had a form designer to this as well. Otherwise changes in the UI destroy your code.

DB

Hello Gnozal,

can you, or would you answer this questions?

Thanks.

1.) pureFORM consists auf only 3 files. But witch other files are absolutly nessessery?

2.) what exakt is going on when i press in the original pb ide the command "make EXE"?

Which files in which format will go with which parameter to which files (linker....compiler....)?

3.) Dito, when press in pureFORM the F6 Command, and/or the F7 Comannd.

Thanks

Hi Gnozal-

gnozal wrote:

ar-s wrote:Hum that is strange,
i have check my directories, PureForm is in the good one (PB 4.51 x86 / plugin (and root as well), the error message :
Why does it take the x64 directory to work ?

It seems that PureFORM has detected your x64 installation.
You can change the compiler path in Preferences : set the path to the x86 compiler.

I encounter the same problem, and if I set the Compiler path in Preferences,
PureFORM seems to delete it again when I start it the next time - the error pops up (with obviously an empty string for compiler path displayed - , but pureform will then run after clicking the error away).

Looking into preferences after that indeed shows an empty field for compiler path, whereas if I look into PureFORM.ini before I (re-)start Pureform, the previously entered Path had obviously been recorded correctly.

AND it seems to be looking for the compiler on the SD card Drive Letter ( I searched all Registry and all .ini Files but couldn't locate a corresponding entry at all (I actually hav run PB from the SD card some times in the past).

Environment:
Win 7-64 Home Premium
PureFORM 1.99 Build 417
PureBasic 4.51 (x86) final release

Yes, I HAD had installed 4.60ß1 x64,
but after reading the previous poster's posting and your replies,
I uninstalled it through its uninstaller.
The error remains the same.

I have - of course - also re-installed PureBasic 4.51x86 and PureFORM
after uninstalling the x64 version of PB. Didn't help!

I am not really sure how I keep doing it -- but several times I have ended up with the "form code" inside of a code-infusion window, and my changes lost..

I'm sure it's a "don't push that button" sort of thing -- but honestly, i don't know what I do to get it in there. is this a common problem or unique to me?

I open japbe then open up my pureform project, made some changes, add some code infusion, hit save; then "update code" and then return to japbe (I thought it integrated tighter and wouldn't have to, but) and then "reload code", and try to run.

at this point -- sometimes it works as expected, other times, my "modified" code in japbe is gone, and then the code sort of "repeats itself" w/in the object I most recently did a code infusion....

Captn. Jinguji wrote:I encounter the same problem, and if I set the Compiler path in Preferences,
PureFORM seems to delete it again when I start it the next time - the error pops up (with obviously an empty string for compiler path displayed - , but pureform will then run after clicking the error away).

I can only repeat what I said : set the path to the x86 compiler in Preferences.
If it doesn't work (I can't think on any reason), you may modify PureFORM.ini directly : FORM_CompilerPath = C:\YourPBx86path\Compilers\pbcompiler.exe

jassing wrote:I am not really sure how I keep doing it -- but several times I have ended up with the "form code" inside of a code-infusion window, and my changes lost..

I'm sure it's a "don't push that button" sort of thing -- but honestly, i don't know what I do to get it in there. is this a common problem or unique to me?

I open japbe then open up my pureform project, made some changes, add some code infusion, hit save; then "update code" and then return to japbe (I thought it integrated tighter and wouldn't have to, but) and then "reload code", and try to run.

at this point -- sometimes it works as expected, other times, my "modified" code in japbe is gone, and then the code sort of "repeats itself" w/in the object I most recently did a code infusion....

If you run PureFORM as a jaPBe plugin, you should not have to reload the code, PureFORM does it automatically before quiting (if you checked 'Reload code in jaPBe after PureFORM closes' in Preferences.
Note that all code between two Start/End tags is replaced.

PureFORM.chm wrote:Full source code update : use function 'Update code in source'

1. Enable the code update feature :

- In Preferences, check 'Add PureFORM tags to generated code'
. The first time, save the generated code with 'Save as code' in the main menu.
. The next time (after you changed the form) you can update the source with 'Update code in source' in the main menu.

2. Enable jaPBe reloading changed code :

- In Preferences, check 'Reload code in jaPBe after PureFORM closes'

Then it should work like this :
3. Open 'MyCode.pb' in jaPBe.
4. Start PureFORM as jaPBe plugin : it will open the project 'MyCode.pbf'.
5. Modify the form.
6. Use 'Update code in source' to update the source.
7. Exit PureFORM.
8. 'MyCode.pb' is reloaded when you quit PureFORM (if project has changed and code has been updated).

Update (build 418)

Changes :
- Custom gadget selector is now a drop down menu in the gadget tool bar
- Added support for OpenSubMenu(Text$ [, ImageID]) in the generated code if detected PB version >= 4.60
- You may add the CanvasGadget as custom gadget :
  Name : CanvasGadget
  Init code : <empty>
  Create code : CanvasGadget(%id%, %x%, %y%, %w%, %h%, %[flags]%)
  Free code : <empty>
  Flags : #PB_Canvas_Border|#PB_Canvas_ClipMouse|#PB_Canvas_GrabMouse|#PB_Canvas_Keyboard|#PB_Canvas_DrawFocus
  Comment : CanvasGadget [Purebasic 4.60+]

Hi!

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 !

If I click on OK button, PureForm starts its GUI

cu,
guido

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.

gnozal wrote:I can only repeat what I said : set the path to the x86 compiler in Preferences.
If it doesn't work (I can't think on any reason), you may modify PureFORM.ini directly : FORM_CompilerPath = C:\YourPBx86path\Compilers\pbcompiler.exe

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.

Let me put it this way:
* Is there corresponding code at all in PureFORM that actively removes the Path entry from the settings and subsequently from the .ini
(be it deliberately or casually by putting "" where a non-empty path string should rather be) when it starts up, reads the .ini file and doesn't like what it sees at the target point in the file system ?
(I really can't think of any malware or similar outside stuff of PureFORM that concerns itself with producing this "oh so funny" misbehaviour )

* 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 (e.g. Helpy as well as me ) ?

* I checked more closely, I would have to have at least one USB stick plus the sd card plugged into my notebook to actually have
drive letter "F:" assigned at all ( something I very rarely do, and almost definitely not at all when I'm using PB or Pureform ).
Could possibly any "default" reference path "F:\..." be hidden deep, deep down in PureFORM's sources, somehow getting applied because
some "if-then"- or "select" - construct falls through "the floor of all anticipated conditions" for whatever reason ?
(No especially french letters visible in the path to the "ghost" compilerfile path, though).

Can I do anything more to track down the problem ?

Hope my wild speculations of what could possibly be are not arriving at your end as offensive,
I really am at a loss what could be a reason on the computer near me .
The windows event logs are quiet on the matter, no "you need authorization for what you are trying to do", nothing.

Kind regards
CJ