Form Designer 5.10

[Polo]

Bug : Run Form Designer and look at the source code of the current window. You forgot InitWindow_0()

I removed it actually. The aim to use the pbf file is to include it into your main project file:

Code: Select all

IncludeFile "myform.pbf"

InitWindow_0()

Repeat
  event = WaitWindowEvent()

  Window_0_Events(event) ; the event procedure is not finished and subject to change

Until 
End

I have just discovered CTRL-D, very very useful.
I found out that repeated objects are not reported in the init_window procedure until you add a new object.

I am also having difficulties with Select all / Copy in code window now, but I remember I had used it many times before.

Both fixed, thanks!

preferences -> custom gadget -> any definitions => CRASH

Fixed.
Please bear in mind the custom gadgets are saved but cannot be retrieved on opening (for now).

[Perkin]

Small fixes version (still beta 9). Flickering should be reduced, and buttons corrected.

Flicker is much much better. Thanks.

[Shield]

Small fixes version (still beta 9). Flickering should be reduced, and buttons corrected.

Flicker is much much better. Thanks.

Indeed!

[Polo]

Good to hear the flickering has reduced

Next beta should be able to save/load custom gadgets, with some limitations.
I've disabled the code editor again, as we decided to focus on the form designer functionalities.
Beta 10 should be released tomorrow

[Polo]

Slowly working on the events, basically you choose a file which contains the event procedure, then you've got a dropdown to select the procedure. You can double click on the procedure selector to open the file in Purebasic IDE
(unlike what is shown on the picture below the file selection is made on the window - so one window = one event PB file).
The FD is already able to save/load these event stuffs, you'll be able to test that on the next beta.

It's not done yet, but the Form Designer will also be able to create the procedure for you if you enter a procedure name that doesn't exist.

The event procedure should be of the form Button_Event(ButtonID, EventType).

[Warmonger]

Looks nice so far! Few more bugs, and suggestions.

Bug: Menu pushes the grid down out of the window frame. Also your padding the window 2px on both of the width and height which creates a disproportionate end result.

I think this is a direct result of the menu problem above.


Suggestions: The design window should take on the same looks as the OS its being used on. On Windows 8 the windows border and title bar looks just like Windows 7, I am guessing it looks like this on XP too (see screen above). Other then that I just started using it few seconds ago and will give it a thorough testing. Also the menu editor could be a bit easier to use if you auto generated its own constants for menu items (first item = #MenuItem_0, second = #MenuItem_1 etc). As it kinda does get very hard to keep track which level is an item and which is as submenu.

Otherwise it still feels far from being complete, but has great potential.

[Polo]

Bug: Menu pushes the grid down out of the window frame. Also your padding the window 2px on both of the width and height which creates a disproportionate end result.

Fixed the menu problem, thanks.

I think this is a direct result of the menu problem above.

Do you mind giving me the generated code for this?

Suggestions: The design window should take on the same looks as the OS its being used on. On Windows 8 the windows border and title bar looks just like Windows 7, I am guessing it looks like this on XP too (see screen above).

If I have to support all Windows skins that's gonna be long. Is that really a big deal? I don't even think Microsoft supports older styles in Visual C.

Other then that I just started using it few seconds ago and will give it a thorough testing. Also the menu editor could be a bit easier to use if you auto generated its own constants for menu items (first item = #MenuItem_0, second = #MenuItem_1 etc). As it kinda does get very hard to keep track which level is an item and which is as submenu.

Otherwise it still feels far from being complete, but has great potential.

Thanks for the suggestions.
Please remember you can make a donation to support the development of this

[Polo]

Also the menu editor could be a bit easier to use if you auto generated its own constants for menu items (first item = #MenuItem_0, second = #MenuItem_1 etc). As it kinda does get very hard to keep track which level is an item and which is as submenu.

Added. The Menu editor can't know if the item is going to be a submenu though (as this is created afterwards) so a constant will be generated for it as well (and will get ignored when saving/code generation).

[Warmonger]

I think this is a direct result of the menu problem above.

Do you mind giving me the generated code for this?

Code: Select all

Global Window_3

Global ListIcon_0

Global Img_0

Enumeration
  #File
  #New
EndEnumeration

UsePNGImageDecoder()

Img_0 = LoadImage(#PB_Any,"C:\Users\Warmonger\Desktop\png\1.png")

Procedure InitWindow_3()
  Window_3 = OpenWindow(#PB_Any, 0, 0, 500, 360, "", #PB_Window_SystemMenu)
  CreateToolBar(0, WindowID(Window_3))
  ToolBarImageButton(#New,ImageID(Img_0))
  ToolBarToolTip(0, #New, "New File")
  CreateMenu(0, WindowID(Window_3))
  MenuTitle("File")
  ListIcon_0 = ListIconGadget(#PB_Any, 10, MenuHeight() + ToolBarHeight(0) + 10, 480, 300, "", 100)
EndProcedure


Procedure Window_3_Events(event)
  Select event
    Case #PB_Event_Gadget
      Select EventGadget()
        Case ListIcon_0
          
      EndSelect
    Case #PB_Event_CloseWindow
      CloseWindow(Window_3)
  EndSelect
EndProcedure

Suggestions: The design window should take on the same looks as the OS its being used on. On Windows 8 the windows border and title bar looks just like Windows 7, I am guessing it looks like this on XP too (see screen above).

If I have to support all Windows skins that's gonna be long. Is that really a big deal? I don't even think Microsoft supports older styles in Visual C.

Every other form designer I have ever used always supported the visual design of the current OS window. I'm sure someone may help you out later with adding/fixing that. It's not a problem really, just more of an annoyance to open the designer up to be greeted with a Vista window when your on Windows 8, or XP. Especially if you're like me and are use to a specific style (keep in mind the controls are in Vista style as well). You should do what every other does, and spawn an actual child window to do the editing on. That way it pertains to whatever version of Windows its used on. The owner of PureVision might be able to give you some pointers on how to do that.

P.S. I feel there should be an option to remove the Event procedure as most people im sure prefer to write their own event loops.

[Polo]

Ok the gadget position is fixed, apparently the MenuHeight() shouldn't be used for positioning, only ToolBarHeight.

Every other form designer I have ever used always supported the visual design of the current OS window. I'm sure someone may help you out later with adding/fixing that. It's not a problem really, just more of an annoyance to open the designer up to be greeted with a Vista window when your on Windows 8, or XP. Especially if you're like me and are use to a specific style (keep in mind the controls are in Vista style as well). You should do what every other does, and spawn an actual child window to do the editing on. That way it pertains to whatever version of Windows its used on.

At the moment controls/window skin is Windows 7 actually.
I'm not drawing a real child window as obviously I would lose the cross platform ability which is what this tool is all about.
I don't have Win8 as it's not properly released yet, though you can still send me a screenshot of a window containing menu/toolbar/statusbar and most of the gadget available and then I can try to add the win8 style.

[Warmonger]

Ok the gadget position is fixed, apparently the MenuHeight() shouldn't be used for positioning, only ToolBarHeight.

Every other form designer I have ever used always supported the visual design of the current OS window. I'm sure someone may help you out later with adding/fixing that. It's not a problem really, just more of an annoyance to open the designer up to be greeted with a Vista window when your on Windows 8, or XP. Especially if you're like me and are use to a specific style (keep in mind the controls are in Vista style as well). You should do what every other does, and spawn an actual child window to do the editing on. That way it pertains to whatever version of Windows its used on.

At the moment controls/window skin is Windows 7 actually.
I'm not drawing a real child window as obviously I would lose the cross platform ability which is what this tool is all about.
I don't have Win8 as it's not properly released yet, though you can still send me a screenshot of a window containing menu/toolbar/statusbar and most of the gadget available and then I can try to add the win8 style.

Eh, visual styles killed it for me. Also Windows 7 uses Vista style scheme, so actually its Vista (ever heard of Vista installer?). I personally think cross compatibility is just a limiting idea and quite pointless.

[Polo]

Eh, visual styles killed it for me. Also Windows 7 uses Vista style scheme, so actually its Vista.

Well, it's still Win7 style

I'm happy to add Win8 style though if I can't get someone just doing a screenshot that's gonna be hard

[Warmonger]

Eh, visual styles killed it for me. Also Windows 7 uses Vista style scheme, so actually its Vista.

Well, it's still Win7 style

I'm happy to add Win8 style though if I can't get someone just doing a screenshot that's gonna be hard

Vista style, but Windows 7 also uses it. Maybe you should consider checking the OS version, and use a template set based on that. That way regardless if your on XP, Vista/7, or Windows 8. The form designer will retain the same visual style. If I get some time I will compile some screens of the official Windows 8 style.

Also some cosmetics with the toolbar's text.

Code: Select all

Save as... -> Save As...
Z Order -> Order
Status bar -> Status Bar

[Polo]

Eh, visual styles killed it for me. Also Windows 7 uses Vista style scheme, so actually its Vista.

Well, it's still Win7 style

I'm happy to add Win8 style though if I can't get someone just doing a screenshot that's gonna be hard

Vista style, but Windows 7 also uses it. Maybe you should consider checking the OS version, and use a template set based on that. That way regardless if your on XP, Vista/7, or Windows 8. The form designer will retain the same visual style. If I get some time I will compile some screens of the official Windows 8 style.

Also some cosmetics with the toolbar's text.

Code: Select all

Save as... -> Save As...
Z Order -> Order
Status bar -> Status Bar

Thanks. I'll sure do a Win8 style, probably not XP though - Microsoft is dropping it soon.

Fixed the cosmetics

[Warmonger]

Eh, visual styles killed it for me. Also Windows 7 uses Vista style scheme, so actually its Vista.

Well, it's still Win7 style

I'm happy to add Win8 style though if I can't get someone just doing a screenshot that's gonna be hard

Vista style, but Windows 7 also uses it. Maybe you should consider checking the OS version, and use a template set based on that. That way regardless if your on XP, Vista/7, or Windows 8. The form designer will retain the same visual style. If I get some time I will compile some screens of the official Windows 8 style.

Also some cosmetics with the toolbar's text.

Code: Select all

Save as... -> Save As...
Z Order -> Order
Status bar -> Status Bar

Thanks. I'll sure do a Win8 style, probably not XP though - Microsoft is dropping it soon.

Fixed the cosmetics

If you generate a form for me to run, I will take a screen of it. So you can add Windows 8 skin support (this way you know what everything is). I run build 9200 of Windows 8 (official final release).

Also I feel as if you should add a checkbox option to Preferences -> General called something like "Generate window events procedure". And remove the Window_0_Events() procedure from being generated by default. This way people who wish to use it can just enable it in the options, tho as I feel most will wan't to code their own event loops.