1. EuWinGUI update
- Posted by Rod Damon <roddamon at bellsouth.net> Aug 08, 2006
- 472 views
Hi fellow users: Andrea sent me a reply to some questions I had about EuWinGUI. I found it very informative and thought you might too. The lastest versions I have tested, now has non-printable key scan. Such as Insert, Delete, Page Up, ETC. Also it now contains color controls, except buttons. These additions plus future additions being added will greatly improve EuWinGUI's capabilty. START OF REPLY:******************** >> I have a program that I'm developing, it is currently about >>3.000 lines long. My question is this: I noticed that I have >>re-declared a few controls more than once in the program. >>Example: Mark = Control(ClickText,................). Actually you are not re-declaring them (the atom Mark was declared once at the beginning of your program) but you are just re-assigning it a value - the new control's ID... >>The program works just fine, >>1. Did you know this could be done? Yes, of course, since in EuWinGUI you don't have to declare the controls' IDs as constant you could even use a same single variable to create ALL of your controls! But obviously this way you won't be able to change or access at run time any controls but the last one you added and whose ID is still stored inside the variable. Basically, if you are creating controls that you know in advance you won't use in any way in your program (for example static texts/labels) you can use a single variable to create them all without fault. BUT if your controls are to receive Events (like the ClickText of your example which is supposed to receive Click or Move Events) you won't be able of handle them but for the last one created control whose ID is still stored into the variable you used to create them all. >>2. Will this cause a memory leak? Not at all. The library stores internally the handles of all the created controls and takes care of clearing them all once the CloseApp() procedure is called to close an application. The library simply doesn't care if you use or not the IDs of the controls you are creating. >>The FEATURE that I told you about last night, now let's >>me declare controls on the fly in procedures when I need >>them, but not if I don't need them. I have programs that use >>controls only on occasion, but not every time the program is >>run. This is great. Please do not fix this FEATURE. There isn't anything to fix there, the library was coded to be able of doing that! The ability of creating new controls on the fly is the one that allows the Window Designer to work! END OF REPLY******************* Rod Damon EuWinGUI is not dead.
2. Re: EuWinGUI update
- Posted by Serge Lavigne <lavigne.s at videotron.ca> Aug 08, 2006
- 468 views
Hi When will this updated version available? When all you have is a hammer, everything starts to look like a nail.
3. Re: EuWinGUI update
- Posted by Jeremy Peterson <ptl99 at hotmail.com> Aug 08, 2006
- 480 views
Glad to hear it. When will the new version be available? Jeremy