PureBasic Forums - English

1) BUG ? I create a new window 2ndWindow that I call from a button in main window, and when I link a code 'A_GLOBAL_VARIABLE = 0' in the event at CLOSE Event of object 2ndWindow, code is executed but 2ndWindow not closed anymore...
Is that normal ? When I have no code in that event, I can close it...

2) optional : is it possible to let the code infusion as a separate object like windows list, gadgets lists...because its not very user friendly to click the object, right click with mouse, open code infusion, write code, close code infusion, test, reopen code infusion, etc...in a future version ?

3) optional : Add custom objects with properties ? (like wxWidgets ?)

Otherwise, nice tool ! I use it !

glops wrote:I create a new window 2ndWindow that I call from a button in main window, and when I link a code 'A_GLOBAL_VARIABLE = 0' in the event at CLOSE Event of object 2ndWindow, code is executed but 2ndWindow not closed anymore...
Is that normal ? When I have no code in that event, I can close it...

It's by design.
If you add code for an event, you have to manage the event, i.e. in this case close the window.
PureFORM adds some code to close the window only if there is no user code available.

Hello Gnozal,

in the ZIP of the update from PureFORM is Build 362, not 363!

hjf

hjf wrote:in the ZIP of the update from PureFORM is Build 362, not 363!

I just downloaded it, and it is build 363.
Maybe a cache / proxy issue ... Could you try again ?
http://freenet-homepage.de/gnozal/PureFORM.zip

Hello Gnozal,

now it works correct.

Thanks
hjf

Hi Gnozal,
I love PureForm. Thanx for your effort and making it available to all.

I'm having some issues on this current project where PureForm rapidly gobbles up all available memory whilst working on the form.
I can reproduce it every time but I don't need to do anything in any particular order. Just working normally then after 10 or so minutes it's taken all available memory (4GB). The work around is to shut it down every 5 mins or so and restart it.
I'm using PB4.2 on Vista 64bit.
I'm happy to forward the project &/or work with U to narrow it down.
Any clues ?

swan wrote:I'm having some issues on this current project where PureForm rapidly gobbles up all available memory whilst working on the form.

I don't know much about Vista, but I heard it is reserving lots of memory for a task compared to XP.

swan wrote:The work around is to shut it down every 5 mins or so and restart it.

Are there any issues apart from the task manager available memory display ?

swan wrote:I'm using PB4.2 on Vista 64bit.
Any clues ?

Not really. I usually work on a PC with 64 Mb total RAM [32 Mb free] (Mb not Gb !) without any problem.
1. Maybe it's a Vista (64) issue ? Could you test your project with WinXP ?
2. Maybe you could post your project so I can test it (with NT4 and XP though).

Apologies for the delay. Too many deadlines at the moment, perhaps I should have waited before posting - no harm !

I tested it on XP 32bit and it doesn't seem to be an issue. I don't have Vista 32bit here to test to see if it's a 64bit or anything Vista issue.

The issue came to light after my machine freezing when using PureForm. Upon investigation it wasn't freezing simply virtual memory kicking in. If I closed PureForm it would clear (back to normal). Viewing the resource graph confirmed it all.
Interesting, within a populated project, if I bumped gadgets around (arrow keys) U can see the memory being gobbled on the resource graph and then freed when closed. So quite repeatable.

PureFORM is a great tool! Thank you gnozal!

I have a little suggestion:

==> In th gadget loop it is possible to choose "Not in event-loop"!

==> It would be helpful, if these gadgets would be not listed in the code infusion window (Gadget Event --> Object --> drop down list). It should stay visible in the Insert enum drop down list.

greetings from germany,
guido

Is PureForm portable?? i.e. does it leave traces in registry some user directories? Does it support relative directory paths in the configuration???

Klonk wrote:Does it leave traces in registry some user directories?

It does not write to the registry. It reads the registry to find PB's installation folder.
PureFORM stores it's preferences in it's own directory (PureFORM.ini).

Klonk wrote:Does it support relative directory paths in the configuration???

I don't know, never tried. I didn't add any specific support for this.

swan wrote:Hi Gnozal,
I love PureForm. Thanx for your effort and making it available to all.

I'm having some issues on this current project where PureForm rapidly gobbles up all available memory whilst working on the form.
I can reproduce it every time but I don't need to do anything in any particular order. Just working normally then after 10 or so minutes it's taken all available memory (4GB). The work around is to shut it down every 5 mins or so and restart it.
I'm using PB4.2 on Vista 64bit.
I'm happy to forward the project &/or work with U to narrow it down.
Any clues ?

I had experienced exactly the same memory leaks with Vista x64 + PB4.20 but none so far with Vista x64 + PB4.30. I don't know if this is only coincidence or problem was in PB4.20.

For the current project I had to convert to PB Visual designer, still with Vista 64 and PB 4.2 just so I could finish it.
But U say something interesting - Pureform doesn't require PB to operate, does it ? If not how could versions make a difference ?

swan wrote:Pureform doesn't require PB to operate, does it ? If not how could versions make a difference ?

If versions don't make difference then it is probably problem with some specific gadget positions. I used a lot of framegadgets and panelgadgets in the project when i experienced these memory leaks but in current project i don't work with this gadgets and it is all working normal. Also, i had one gadget with negative x and y positions completely off window area accidentally created that i later discovered. Something of that probably caused leaks. This is only my guess.

I've chalked it down to just another incompatibility with Vista64 and moved on. One day we'll all be using 64 bit OS's ...