PureBasic Forums - English

Ok thank you.
One last thing : what will be the "real" name of Form Designer ?
I mean, in some betas, it is spelled "Form Designer", and in others, "FormDesigner"
And even the name of the executable file (in Contents/MacOS is sometimes spelled "Form Designer" and sometimes "FormDesigner"....

By the way, in the last beta of the IDE, launching the visual designer (CMD Y) with the native entry from the tools menu doesn't work. Maybe an issue due to what i explained above ?
Or a bug of the IDE ?...

Thank you !

I don't really control that, but the name doesn't matter much as when it'll be included in the IDE it will have no name at all

You mean, it will be a part "inside" the IDE, not an external app ?

In the future yeah!

Great !

It would be nice for the PureBasic IDE to work exactly like Visual Basic. In a sense you can create your form, and code its functionality in real time. Maybe add a little popup box to the IDE asking what type of application would you like to create (GUI, Console, etc), or to open a existing project.

Maybe a planned feature in the future ?

Warmonger wrote:It would be nice for the PureBasic IDE to work exactly like Visual Basic. In a sense you can create your form, and code its functionality in real time. Maybe add a little popup box to the IDE asking what type of application would you like to create (GUI, Console, etc), or to open a existing project.

Well it's basically what's happening right now isn't it? You create the form and can edit the event procedures from the FD

when the unicode support??

I thought Fred had added it, he'll probably do it soon

Gaetan,
I have downloaded the latest beta and I have two questions:

what's the best way to use FD in a very simple application?
Maybe a simple example with a pbf file and a pb file with some event procedures would be really useful to explain the workflow with this new tool.

And the second question is: is there a way to add menu events (and relative shortcuts) in code generated by FD?

I probably should do an example, though I might wait until it gets merged into the IDE so that I can do a proper help page or something!
Basically the best way to use it is to have one form, one event .pb file per form, and then one main .pb file which includes the .pbf files and initialise the windows

There's no event support for menus yet, though now I've redone the whole menu editing I should add it!

Basically the best way to use it is to have one form, one event .pb file per form, and then one main .pb file which includes the .pbf files and initialise the windows

Thanks, that's what I am doing. I use the PB IDE to edit pb files only and FD to edit the pbf form.
I have put the files inside a project so that form-generated variables, constants and procedure names are scanned and ready available in the PB editor too.

luciano wrote:

Basically the best way to use it is to have one form, one event .pb file per form, and then one main .pb file which includes the .pbf files and initialise the windows

Thanks, that's what I am doing. I use the PB IDE to edit pb files only and FD to edit the pbf form.
I have put the files inside a project so that form-generated variables, constants and procedure names are scanned and ready available in the PB editor too.

Looks nice!

Added event support to Menu and Toolbars. It supports constant sharing.
Fixed menu item selection which was a bit difficult if you had a toolbar in the window as well.

Menu/Toolbar procedures should be like this:
(the actual procedure name doesn't matter).

For shortcuts you can add them in the menu items, it will be displayed but the actual shortcut won't be created in the pbf file. I probably can add it easily, I'll see.