ProGUI V1.38 UI Library (Small Bug Fix)

[Zach]

Nope, that was one of the first things I tried :p

Its probably a lot more convoluted than that..

I suppose it is important to point out that while I did my best to provide a sample, my actual project structure is a lot more complex. I do not keep the event loop in the same file, nor my ProGUI startup commands.

Funny thing about that is, I've noticed people using ProGUI_Init() and that always crashes with an IMA - I don't think I've ever used it.. Nor have I ever used ProGUI_End()

That being said I doubt they are the problem Pretty sure I took those lines out when testing your solution. I'm wondering if I am losing some awareness with some of the code split up into other files but I'm not even sure what the problem could be. I've already tried shuffling around include orders and that made no difference either.

If anyone wants to look at the whole project, I'd be obliged to send you a zip.

[Zach]

In fact there must be something goofy with the whole project. Perhaps I need to recreate it and rebuild the GUI slowly.

Because I just realized that the rebar does not work in my code either. It just stays as a blank white space.. This is really, really strange and I'm not sure what the deal is.

[GoodNPlenty]

Funny thing about that is, I've noticed people using ProGUI_Init() and that always crashes with an IMA - I don't think I've ever used it.. Nor have I ever used ProGUI_End()

Sorry I left ProGUI_Init() and ProGUI_End() in the example since I was including the ProGUI source from the Platinum Package.

In fact there must be something goofy with the whole project. Perhaps I need to recreate it and rebuild the GUI slowly.
Because I just realized that the rebar does not work in my code either. It just stays as a blank white space.. This is really, really strange and I'm not sure what the deal is.

I've had that happen before where after adding a some features some original items quit working. Sometimes I have been able to comment out items till I found the problem and other times I found starting over was easier.
I'm sure you will get it going, if not I'd be happy to look at your code, as sometimes a second set of eyes can help.

[Zach]

I have become fairly convinced it has to do with the way I am breaking up my source code into different files, but I can't understand why.
Even an attempt to create a simple window with rebar and dropdown menu still has this bug occuring, while the other examples that keep the GUI Drawing and Event Loop together do not. And that is really the only significant difference between code examples, is that my event loop is contained it an upper-level file, which includes a "header" file where all the GUI drawing is taking place.

(the intention is to keep the event loop separate so I don't have to recreate / copy it to another file if I do a Linux GUI, etc)

I am using EnableExplicit and defining variables and declaring procedures, and it compiles without complaining so I am at a loss as to what is getting messed up.

I have moved the project to its own Tree and removed my ProGUI_PB.pb file so users will need to provide that and place it in the "Includes" folder. Also place a ProGUI.DLL in the MWedit folder if needed. I did this for file size reasons. I have also obviously modified the startup call to run in Demo mode for obvious reasons. Those are the only changes. Just drop those two files in and it should run. Very interested to find out if it bugs on other peoples machines or not (hoping it does, since self contained examples in a single file, seem to work for me)

You may or may not find other areas of critique, since I'm an amateur, but I'd like to keep it focused to only those problems which cause this issue (if it can be identified)

PurebasicProjects.zip
Project can be opened via MWEdit.pbp
Also: My original drawing Procedure is renamed with an _old appendage. The current render is just my attempt at a basic window. But the old code is still there to look at.

[Zach]

And just a final note. I have begun to rebuild the project from scratch, slowly porting over previous files, etc.

So far I am not experiencing the bug, although I am structuring things a little differently anyhow. It seems I am still able to keep my event loop separate (I am just keeping it in the compile target this time) without incident..

I wonder if for some reason... the project just went goofy because of using it through various PB upgrades or something. I have tried back-porting all kinds of changes I am making while doing the new version of the project and none of them have any effect.

Maybe one day I will figure out what went wrong

[Zach]

Making good progress and my project is almost back to the point where I had it, in the new Project now.

However I think I may have found another bug, if anyone could confirm this.

When creating a rebar, it does NOT like a MenuEx created with #PB_Any / #ProGUI_Any despite the manual listing this as valid syntax during Menu creation. No error is given and the Rebar silently fails to render.

It seems the Rebar will only accept Integer or Enumerated Constants as Menu ID's, even though the Menu shows up and works fine in any of these cases (Int, Enum, #PB_Any, #ProGUI_Any)

[Poshu]

Making good progress and my project is almost back to the point where I had it, in the new Project now.

However I think I may have found another bug, if anyone could confirm this.

When creating a rebar, it does NOT like a MenuEx created with #PB_Any / #ProGUI_Any despite the manual listing this as valid syntax during Menu creation. No error is given and the Rebar silently fails to render.

It seems the Rebar will only accept Integer or Enumerated Constants as Menu ID's, even though the Menu shows up and works fine in any of these cases (Int, Enum, #PB_Any, #ProGUI_Any)

You should post code for us to check...

On another subject, I've added drag and drop support (inspired by easyvent) for some ProGUI gadget; unfortunately, chris is still missing in action and I still can't release a working patch...

[flaith]

Hi everyone,

do someone got news from Chris ?

i just bought ProGUI but I still waiting to receive the files and license key

[electrochrisso]

Last I heard was Chris got a coding contract and moved to another part of UK, and will be a quiet for a while, so he can concentrate on the contract code and make some money, I hope he is doing ok.

[flaith]

I hope too, thanks for the info electrochrisso

[Karellen]

I guess, that's what happens to most "one man projects" sooner or later. However, it's frustating to watch the author simply disappear after having purchased the professional lib with lifetime support. I'm about to start a bigger project and sadly have to waive progui.

@Chris: Imho a sign of life would be adequate to give a clue to your customers if and how things might develop.

[Poshu]

Tried to contact him every way I could, but still got nothing. I'm still looking for a way to release update for the current branch of progui while we wait for the allmighty version 2...

[Karellen]

Tried to contact him every way I could, but still got nothing. I'm still looking for a way to release update for the current branch of progui while we wait for the allmighty version 2...

First of all, thanks a lot for your efforts about that update, I've been following this since a while and really appreciate it!
Personally I don't count on V2 anymore. Would have been great, but who knows if it ever shows up. What I really need is a reliably maintained version for 5.20 LTS as userlib.
Since Chris isn't even *answering*, things are looking too bad for my taste. I'm out here, no professional work possible that way, sad but true.

[Poshu]

Let me a few more tries, I just found him on facebook.

Well, while we wait for a more official solution, I can give you some support: mail me a compiled program using progui (like an example from the proGUI's package) without the 5 minutes limit and I'll mail you back a working library :p

[flaith]

Just received the source code and keys