PureBasic Forums - English

Rook Zimbabwe wrote:How hard would it be to create a preferred template for the included code looP... You know I work a different code loop than most people but I like it... If there was some way to template that (for me or anyone elses preferred format) that might be a cool feature!

I don't know, what is you code loop format ?
Currently, you have 3 options :
- no event-loop code generated
- if/elseif/endif event-loop code
- select/case/endselect event-loop code
If your favorite template is too different from the 'standard' one, it may be difficult for PureFORM to handle it.

Phillippe... I use one style and have been experimenting with 2 other methods... give me a second to locate and I will include the link where this was brought out to my attention on the forum!

http://www.purebasic.fr/english/viewtop ... 13&t=40644

Program organization has info about the three styles...

Mine - which is simply like the style in the Aplha VD and I like it much!
Foz - which I have been experimenting with and seems to work nice but I have to rebuild my Application from scratch to make it work with all my gadgets

and

TS - Soft suggestion which looks very logical and nice but I have trouble with over 298 gadgets in total but I am stil monkeying with...

Rook Zimbabwe wrote:Phillippe... I use one style and have been experimenting with 2 other methods... give me a second to locate and I will include the link where this was brought out to my attention on the forum!
http://www.purebasic.fr/english/viewtop ... 13&t=40644

The (new) VD alpha style looks interesting, maybe I can implement it when I have some time. But which variation ... I like the map idea, but it's PB4.4x only.
And maybe new VD (final) will have yet another style ?

Well I KNOW you have nothing to do but work on PUREform...

How about the option...

Or my idea of a schema format so it could be set up as wanted? I know the initial would probably be involved but once in code it would simply be a tweak...

OK I am going to look at the implementation of such a concept. If I get anything I will post it!

From http://www.purebasic.fr/english/viewtop ... =4&t=41040 :

ozoffi wrote:These are things struck me the following with PureForm:
- There is apparently no copy of several Gadgets at once.

Use gadget groups : select several gadgets using mouse or keyboard, right-click -> Save group to [Temp group], right-click -> Copy/Move gadget group -> [Temp group].

ozoffi wrote:- If for example chosen for such ComboboxGadget one Baloontipp crashes PureFORM.

No crash here when I add a tooltip to a ComboboxGadget. Please post your form [.pbf].

Hi!
Thanks for the info - I tried it always with ctrl-c and ctrl-v.
Apparently, the crash happens only when the group gadget window is open. I was involved with the project, in which I had yesterday the problem - now everything works ...
I will observe and possibly re-post.

Regards
Oliver

This has got to be one of the most usefull utilites for deving in PB.

I've been using this quite heavily for the last few weeks and I have to say it's saved me loads of time.

A couple of points / q's

the show / hide options don't seem to inject the relevenat code - is this correct ??

Also, when merging forms, it doesn't matter if you choose to let pureform handle enumeration or not - it still replaces some enumeration.

E.G in my forms i use a number as a prefix - so #form0010 and that prefix is rolled through the form - #lbl_0010_1 or #btn_0010_add.

However when i merge two forms the original form is re-enumerated - #frm0010 - becomes #Window_0 etc.

Finally, it would be a godsend to be able to find/replace #names in the code or set up naming preferences ( replace button with btn ) as this has to be done by hand if you are following a schema.

Brillinat program though.

Cheers

captain_skank wrote:the show / hide options don't seem to inject the relevenat code - is this correct ??

Yes, it's only for form designing. It can be handy if you have several layers of gadgets.

captain_skank wrote:Also, when merging forms, it doesn't matter if you choose to let pureform handle enumeration or not - it still replaces some enumeration.

If you uncheck 'Adapt gadget enumeration', the enumerations should no be modified during the merge procedure. It seems to work here on some (quick) tests.
However, the new created gadgets will be enumerated according to the current settings in preferences.

I upgraded to latest version, and when merging two files it still replaces the enumeration on the subsequent windows with #window1,2,3 ... etc.

Anyhoo - a quick question, I'm clearly doing something wrong, but why do my forms always look different in the Pureform to those diasplayed in PB ?? Is it an XP themes thing ? and if so, how do I make them look the same - the PUREFORM version looks way better.

Ta muchly.

captain_skank wrote:a quick question, I'm clearly doing something wrong, but why do my forms always look different in the Pureform to those diasplayed in PB ?? Is it an XP themes thing ? and if so, how do I make them look the same - the PUREFORM version looks way better.

It may be a themes issue, but the forms shouldn't look very different.
PureFORM is compiled with PB3.94 which may behave differently than PB4.4x.

You can test the form with the compiler version you are currently using with 'Compile/Run' F6 [without XP themes] or F7 [XP themes enabled].

Thanks muchly, F6 and F7 make that clearer now.

However my forms seem to default to the f7 view in pureform but look like the f6 view in PB, so the question is how do i get them looking like the f7 view.

Thanks a lot and sorry for the silly q's

cheers

captain_skank wrote:Thanks muchly, F6 and F7 make that clearer now.
However my forms seem to default to the f7 view in pureform but look like the f6 view in PB, so the question is how do i get them looking like the f7 view.

I guess you have to activate the 'XP skin support' (in jaPBe : 'Project options', in the PB IDE : 'Compiler options').

Bug.

Add a scrollarea to an empty form and scroll vertically to the bottom. Add a button to the scrollarea. Now try and resize the button by dragging the top edge. Here the button jumps massively in size. Would seem to be a problem of coordinate mapping etc.

srod wrote:Add a scrollarea to an empty form and scroll vertically to the bottom. Add a button to the scrollarea. Now try and resize the button by dragging the top edge. Here the button jumps massively in size. Would seem to be a problem of coordinate mapping etc.

Confirmed, should be fixed in next build.

Update (build 386)

Changes :
- fixed gadget resizing issue in scrolled ScrollAreaGadget