PureBasic Forums - English

No doubt - and I wouldn't actually begrudge paying twice, in fact I think that would be pretty fair - just wanted to clarify the position

Zach wrote:Chris, I couldn't remember if you said this, but I could have sworn you said issues with the Frame3D transparency and mismatched coordinates issues I was having would be fixed as well, and no longer require that transparency hack you gave me??

Hey man, yep It's fixed now and you don't need to use the transparency hack any more or parent the controls to it (as it's "real" window is completely hidden). I've sent you an email with the latest beta attached as requested I'm thinking of maybe setting up some sort of official beta repository on the site?

electrochrisso wrote:

complete with live feed webcam and web based remote "prod with hot iron poker robot" button that you can press when I'm slacking heheh

If you must, I was thinking more on the lines of a French maid.

haha well now that would be awesome (a french maid walks in when you press a button), you would have to use it as a reward button though because not much work would get done otherwise

DoubleDutch wrote:The new stuff you are planning sounds great.

Thanks Anthony mate heres an image dump of a current test "super buffer" showing the 2D bin packing algorithm and new Img commands working nicely!

greyhoundcode wrote:Sales question: if you're planning to shift everything to DirectX that's going to be a considerable piece of work. If someone buys a Platinum license is that only going to be valid for the current branch of ProGUI?

No absolutely not, the Platinum license covers the entire life of the product as a reward to those who "invest" early

Zach wrote:Though in all our discussions about upcoming features and major work like this, Chris has so far never hinted that there would be new license purchases required.

I think when I first came across ProGUI I discussed his licensing with him and may have given him an idea or two (can't remember, not really trying to claim credit), I don't remember the license options at that time.. It was either the Lifetime, or the less expensive minor updates, which got added after that.

Yep I think you might have Zach - just tried to keep an affordable pricing model for everyone.

Zach wrote:But I know Chris seems like a fair an equitable person, so if there are any upgrade fees, I'm sure they would be reasonable, especially for long-time current users

Thanks dude nope there will never be any upgrade fees for Platinum users - that's why the licence is valuable, it helps me out with the short term money while developing ProGUI and as a reward the Platinum user saves considerable money on future updates that Standard and Gold users would have to pay to upgrade for.

Anyway I hope that clears the pricing model up a bit more with the Platinum license

Chris.

greyhoundcode wrote:No doubt - and I wouldn't actually begrudge paying twice, in fact I think that would be pretty fair - just wanted to clarify the position

Damn you would have paid twice!? only joking

Chris.

Chris,

I got your email, thanks for sending those files! But there is a problem with the Userlib and I am hoping it was because you didn't include a new ProGUI.res Residents file.
The render speed seems to be fine after modifying my project for DLL use, but I haven't removed the transparency hacks yet and I think (hoping) it is what is causing some bugs.

edit: Nope I went back and checked. It is present in the Explorerbar Demo from the Examples folder also.. I will email the pic to you.

A beta repo sounds like a neat idea. But don't take on too much at once, keeping Beta builds updated every time you make huge changes is probably a lot of steps and a pain.. One or two Beta releases might be a good idea though, as you work on new version updates..

PrincieD wrote:No absolutely not, the Platinum license covers the entire life of the product as a reward to those who "invest" early

...

Thanks dude nope there will never be any upgrade fees for Platinum users - that's why the licence is valuable, it helps me out with the short term money while developing ProGUI and as a reward the Platinum user saves considerable money on future updates that Standard and Gold users would have to pay to upgrade for.

Anyway I hope that clears the pricing model up a bit more with the Platinum license

That's actually really fantastic - you just sold another platinum license

Zach wrote:Chris,

I got your email, thanks for sending those files! But there is a problem with the Userlib and I am hoping it was because you didn't include a new ProGUI.res Residents file.
The render speed seems to be fine after modifying my project for DLL use, but I haven't removed the transparency hacks yet and I think (hoping) it is what is causing some bugs.

edit: Nope I went back and checked. It is present in the Explorerbar Demo from the Examples folder also.. I will email the pic to you.

A beta repo sounds like a neat idea. But don't take on too much at once, keeping Beta builds updated every time you make huge changes is probably a lot of steps and a pain.. One or two Beta releases might be a good idea though, as you work on new version updates..

Hey mate, I've confirmed the bug and I'll send you some new beta files soon - just been beavering away at the new Img command subset and image memory management system. Initial speed results are bloody quick! (with semi-transparent real-time re-sized buffer with alpha channel blitted ontop of another animating) lol

I'll probably leave the beta system for the moment as like you said, it would be too much unnecessary extra work.

greyhoundcode wrote: That's actually really fantastic - you just sold another platinum license

Thank you very much greyhoundcode!

Chris.

I have a question.
I finally started rebuilding my current GUI with the new Map system to keep track of my GUI Elements and easily reference them. I realized that, uh oh I may need to come up with convoluted label names to go with text labels for each of the PanelEx pages - but I decided to play around and see if I could get away with reusing the same name on different pages and it worked!

The thing is, I don't understand WHY it worked. Initially I just copied the code section and forgot to change the target Page, so the label text for the target I had in mind, was actually appearing on the page whose code section I had copied.. But after I changed the target page to the correct page, it did indeed work and both pages have their own unique label..

Why?
This is the code I have used, and switching back and forth between the pages works flawlessly and the title changes.. My hypothesis is that its value in the guiMap is being overwritten - but that can't be?? These procedures only run once if I understand correctly.. They are called while initializing my PanelEx indexes, and I display them based with Event Triggers (that's what the globals are for)

Do I misunderstand or is there really something else at work here? I'm not bothered by it, as long as this works and is considered "Correct" and won't cause problems with my program in general.

PrincieD wrote:This is the code I have used, and switching back and forth between the pages works flawlessly and the title changes.. My hypothesis is that its value in the guiMap is being overwritten - but that can't be?? These procedures only run once if I understand correctly.. They are called while initializing my PanelEx indexes, and I display them based with Event Triggers (that's what the globals are for)Do I misunderstand or is there really something else at work here? I'm not bothered by it, as long as this works and is considered "Correct" and won't cause problems with my program in general.

Yes you're correct with what you thought Zach, the map (guiMap) is overwriting it's entry for "Page_Title" with the new TextControlEx ID each time it's assigned, the different text labels display correctly however because they've been created on the different pages without any problems (just the tracking of the ID's is being lost/overwritten).

Chris.

New version out guys! see top of thread

Chris.

Just an important note about the new build:

If your existing code has Frame3DGadgets inside a PanelEx then previously you needed the following "transparency" hack:
Which will cause bugs until the code is changed to:
The TextControlEx no longer needs to be parented to the Frame3DGadget and will also be positioned relative to it's page instead of the Frame3DGadget (which now doesn't have a "real" window as it is rendered directly onto the PanelEx buffer).

Chris.

Great work, keep it up

I haven't had time to try the new version yet, but I'll let you know of any bugs I find

You have been busy squire, thanks.

Zach wrote:Great work, keep it up

Thanks mate!

Zach wrote:I haven't had time to try the new version yet, but I'll let you know of any bugs I find

I appreciate that Zach, It's difficult for me to fully test under all circumstances especially when there are significant changes "under the hood" like with the current build.

electrochrisso wrote:You have been busy squire, thanks.

Hehe you're welcome mate, yes I'm busy working on the new Image subsystem at the moment which is working rather nicely! been testing it out by doing a screen dump of the packed super buffer (1024 x 1024) at 60fps (it blits ridiculously fast when no delay in the loop lol). I'm currently coding a housekeeping thread that runs in the background re-packing the super buffer/s with images that are accessed most frequently which is performed over a number of frames so doesn't effect the speed of rendering at all

Chris.

Hehe you're welcome mate, yes I'm busy working on the new Image subsystem at the moment which is working rather nicely! been testing it out by doing a screen dump of the packed super buffer (1024 x 1024) at 60fps (it blits ridiculously fast when no delay in the loop lol). I'm currently coding a housekeeping thread that runs in the background re-packing the super buffer/s with images that are accessed most frequently which is performed over a number of frames so doesn't effect the speed of rendering at all

That's great stuff Chris, I expect that ProGUI should be good for animations and certain types of game programming too then.

I'm having a major problem!

I finally sat down and had some time to install the new version of ProGUI.. I deleted the DLL, and PBI include so I could switch back to Userlib version..

I installed the ProGUI userlib in the correct folder and I installed the ProGUI.res in the Residents folder.

However when I run my program, my explorer bar menus do not behave properly!

The Collapse/Expand behavior seems to be causing something to happen that takes up processing power and it hangs for 10+ seconds before updating the Collapsed/Expanded state. It does not play animations for Collapse/Expand either.. During the time it is "hanging" the program constantly takes up 25 CPU usage in task manager.

Windows 7 (x64) SP1
Purebasic 4.61 Beta 1 (x32)
ProGUI v1.34 Userlib Version

edit:
I loaded the Explorerbar Example source code into my PB and compiled and it exhibits the same behavior, so I'm fairly certain it isn't my code. Can anyone else please confirm this bug?

Edit2:

This bug is not present in the DLL version.. This seems to be a UserLibrary issue.... maybe I'm going to have to give up on Userlibs The last one (The beta you sent) and now this official release, seem to be buggered up

I really like the UserLibrary because of the assistance on commands / parameters in the PB statusbar (like with internal PB commands)