PureBasic Forum

Using PureForm -- open a window, add a container, now add a 2nd container.
Then set the back colour of the second one to white
Now uncheck/recheck "background" and Enable purecolor.... they seem to have minds of their own.

This is a PureCOLOR issue.
PureFORM uses PureCOLOR internally (as it is compiled with PB3.94, which does not support gadget colors).
Like stated in the PureCOLOR help file : "Class issues : for better result (less flickering), PureCOLOR uses SetClassLong() to color PanelGadgets, ContainerGadgets and PureScrollAreaGadgets. This means that if you colorize one gadget, all gadgets within the same class will have the same colors".
You may switch to the PB genuine coloring functions for the generated code though. (see Preferences)

Hello Gnozal,

When do you plan to extend PureForm to the new features of PB4.6 (canvas gadet etc)

michel

When I have time to upgrade the code to PB4.xx...
Anyway, did you check the custom gadgets feature ? You can easily add the Canvas Gadget...

Hello Gnozal,



I had forgotten this option

Michel

It would be nice if there was a way to save a "template" group; and have it keep the text in the gadget, and all "code infusion" along with it.

I have a set of gadgets i use that is in a container, it would be nice to be able to save the container & code & sub-objects.

Was editting a container and some objects, hit save and...

Unfortunately, the crash is at the end of the window callback, so not very informative.

Btw, the latest build is 425.

Was editting a container and some objects, hit save and...


It keeps happening - is there some way to avoid it, other than the obvious?

Also -- a while ago; I showed how selecting a colour background for a container caused problems, any chance that'll get addressed?

I can't reproduce it, sorry...
(Btw, the latest build is 425).
I already answered this one, iirc.

I "get latest" every few days...


thanks; I missed it.

Hello Gnozal,

Working a lot with PureFORM and the PBeditor, i find that the menu points:

-> save as code
-> update code in source

are too close.
In order to increase safety I suggest to move one of both, or another idea:
when hitting save as code a popup should remind the user that this command erases all code in the source.

michel, that is a good suggestion, because you can easily loose your extra work. It reminds me of the PB IDE
problem with the X box too close to the up arrow on the code view slide bar. Your looking at the code, and you
accidentally click the x box when your hand slips a little, and poof! - your code you've been looking at is closed.
Fortunately, it does have the MessageRequester box the allow you to cancel if you changed any code - but it's
irritating.
But at any rate, Gnozal, this sure is an excellent and useful program!
Thank you many many times for for sharing this program.

Update (build 426)

Changes :
- 'Save as code' will ask for confirmation before replacing an existing file.

Hello Gnozal,

Perfect, thank you

Michel