PureFORM 1.99 (yet another FORM designer)

[NoahPhense]

Update

Changes :
- fixed a bug in gadget group move if snap to grid was activated

Code Infusion & Reload Code in Japbe ..

I use japbe and pureform .. but i feel i may not have it all setup nice.

What is the best way to set them up together so that they can play nice..

- np

[gnozal]

Code Infusion & Reload Code in Japbe ..

I don't use it a lot myself, I mostly added this because of user requests.
I use the old copy [in PureFORM's code view] / paste [in jaPBe] method !

I use japbe and pureform .. but i feel i may not have it all setup nice.
What is the best way to set them up together so that they can play nice..

Like this (example from PureFORM FAQ) :
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. 'MyCode.pb' is reloaded when you quit PureFORM (if project has changed and code has been updated).

[NoahPhense]

Ok, I see most of that, except I don't see pureform as a plug in.

As for cut and pasting. That's not going to be an option.

I may be miss understanding you. Let me clarify.

The new PB VD Alpha 15, allows me to open .pb in it. And it doesn't
disturb ANY of my hand written code. So, ie, if I make a form, then
I go into Japbe and edit it, etc.. then close japbe, and reopen the pb
in the new VD, all of my hand code is still there, even when i UPDATE
my form, etc..

Making my work seamless.

- np

[GeoTrail]

I agree. The alpha 15 is just great.
Only thing missing is that it doesn't seem to create event procedures.

[NoahPhense]

I agree. The alpha 15 is just great.
Only thing missing is that it doesn't seem to create event procedures.

Mine does.. for the main window, and for every control.

What the problem is, is that to VD itself doesn't remember your settings.

So each time you launch it, you have to go into Project Options and set it.

And even sometimes you have to go the properties window for the control
and check the EventProcedre check box..

Some minor glitches, but it works great.

- np

[gnozal]

Ok, I see most of that, except I don't see pureform as a plug in.

PureFORM is seen as a plugin if placed in jaPBe\Plugin and then started from the jaPBe tools menu.

The new PB VD Alpha 15, allows me to open .pb in it.

Sorry, PureFORM doesn't open a .pb file.

[Klonk]

Just one thing (maybe I'm wrong):
When using your multilanguage procedure READLANGUAGEFILE there is a line:

Code: Select all

PokeS(*LngMemoryPointer + 8, sID + sText, #PB_Any, #PB_Ascii)

I think it should be #PB_UTF8 instead of #PB_Ascii. Otherwise there might be a problem when the application is compiled in Unicode. (As I said maybe I'm wrong, but translations could also contain unicode characters...)

[gnozal]

Just one thing (maybe I'm wrong):
When using your multilanguage procedure READLANGUAGEFILE there is a line:

Code: Select all

PokeS(*LngMemoryPointer + 8, sID + sText, #PB_Any, #PB_Ascii)

I think it should be #PB_UTF8 instead of #PB_Ascii. Otherwise there might be a problem when the application is compiled in Unicode. (As I said maybe I'm wrong, but translations could also contain unicode characters...)

You are right, the translation is forced to ANSI if the compiler is in Unicode mode.
Otherwise, the functions would need to be modified.

[gnozal]

Update (build 245)

Changes :
- new function 'Update window / gadget props in source' [main menu]
Updates the windows and gadgets properties in the source file (MyProject.pb) for the current project (MyProject.pbf).
Gadgets and windows are identified in the source code by their enumeration value. This function only updates the PB properties, it does not update colors or resize information, does not add new elements nor does it update other portions of the code (like enumerations, includes, events, etc...).
Unlike the 'Update code in source', this function works regardless of the 'Add PureFORM code tags to generated code' status in Preferences.
- help file updated

[michel]

Hello Gnozal,

I've problems with the code update since your build 245; the source file is no longer uddated if i execute "update code in source".
Could you please check

michel

[gnozal]

I've problems with the code update since your build 245; the source file is no longer uddated if i execute "update code in source".
Could you please check

Fixed in build 246.
One function call got lost

[michel]

Hello Gnozal,

Thank you for your quick debugging

michel

[michel]

Hello Gnozal,

I discovered the following problem:

When you insert a menu point between existing menu points, the new inserted point gets the event code of the next point?!

michel

[gnozal]

I discovered the following problem:
When you insert a menu point between existing menu points, the new inserted point gets the event code of the next point?!

Yep, I know, the menu / toolbar item event code is currently linked to the item order. In the current WIP version, each menu item has a unique ID.

[Kurzer]

In the current WIP version, each menu item has a unique ID.

*smack* (:lol:) I love to read this!