Page 69 of 103
Posted: Thu Aug 21, 2008 12:01 pm
by gnozal
ozzie wrote:When I add another Window the Enum properties of all the existing gadgets are re-generated to the constants set according to the 'gadget enumeration' preference.
That's odd.
This is not supposed to happen ... could you post the procedure to reproduce the problem ?
Works ok here :
1. New Project
2. Add Button 1 to window 1
3. Edit Button 1 enumeration to '#Test'
, press Enter
4. New window
5. Button 1 enumeration is still '#Test' (and not '#Button_0' for example)
Are you sure to validate the new enumeration after you changed it using 'Enter' or the 'Validate enumeration' button ?
Posted: Thu Aug 21, 2008 12:08 pm
by ozzie
gnozal wrote:Are you sure to validate the new enumeration after you changed it using 'Enter' or the 'Validate enumeration' button ?
That's probably what I'm not doing. I've just been tabbing out of the field, and the name I've entered has taken effect until I add another window. I'll try again making sure I use 'Enter' or 'Validate enumeration'. I'll let you know how I get on.
Posted: Thu Aug 21, 2008 11:18 pm
by ozzie
Found the problem, and it's due to having my Gadget enumerations preference set to WinEnum/Class/Nb. Although I want to set my own Enum constants, I want to start each such constant with the window Enum. So the scenario to reproduce the error is as follows:
- Open Setup / Configuration, and under Code 1 set Gadget enumeration to WinEnum/Class/Nb, and then click OK
- New project
- Change the Enum for the first window from #Window_0 to #wSP
- Add Button to this window
- Change the button's Enum from #wSP_Button_0 to #wSP_Test, and press Enter
- New window
- The Enum of the button on the first window is still #wSP_Test, but if I now change the Enum of the new window from #Window_1 to #wMN then the Enum of the button on the first window is re-generated as #wSP_Button_0
So I think what is happening is that if I use a Gadget enumerations preference that contains WinEnum then if I change the Enum of one window then the Enum properties of the gadgets in ALL windows are re-generated, not just the gadgets (if any) in the current window. The work-around is to set the Gadget enumeration preference to Class/Nb (or probably any setting that doesn't contain WinEnum).
Posted: Fri Aug 22, 2008 9:10 am
by gnozal
ozzie wrote:Found the problem, and it's due to having my Gadget enumerations preference set to WinEnum/Class/Nb.
Thanks for the good report !
PureFORM redefines the gadget enumerations when you change a window text or enumeration and the gadget enumeration scheme is based on window text or enumeration. The bug was I forgot to check a gadget's parent window before applying the change. This should be fixed now.
Additionally, PureFORM now asks for permission before changing the gadget enumerations.
Download
updated (build 341)
Posted: Fri Aug 22, 2008 9:38 am
by ozzie
Yup - that's fixed it. Many thanks for the quick response.
Codeinfusion gone missing
Posted: Fri Aug 22, 2008 8:05 pm
by storck
Hi!
I have been away from PB for a while. I am not sure if it's me or PureFORM. For some reason I can't find code infusion any more. I'm using build 341. It's not in the edit menu and I can't right click to make it appear. It has always worked in the past. Could I have messed with some settings or is it a bug?
Regards,
Storck
Windows XP SP3, PB 4.20, PureFORM 1.99.341
Re: Codeinfusion gone missing
Posted: Sat Aug 23, 2008 7:34 am
by gnozal
storck wrote:For some reason I can't find code infusion any more. I'm using build 341.
Code Infusion is not available if :
- 'Use Scintilla' is disabled in 'Preferences'.
- 'Use Scintilla' is enabled in 'Preferences' BUT PureFORM couldn't load 'Scintilla.dll' and/or 'SyntaxHilighting.dll' (it searches for Scintilla.dll in %Purebasic%\Compilers\ and for SyntaxHilighting.dll in %Purebasic%\Library SDK\Syntax Highlighting\. This maybe a PB path detection problem. You can still copy both DLLs to the PureFORM directory and it should work.
Posted: Sat Aug 23, 2008 8:10 am
by storck
Works like a charm. Thank you once again for an excellent tool!
/ Storck
Posted: Sat Aug 30, 2008 9:59 pm
by nicolaus
@gnozal
can you add MDI gadget support in PureFORM?
Thanks,
Nico
Posted: Mon Sep 01, 2008 8:02 am
by gnozal
nicolaus wrote:can you add MDI gadget support in PureFORM?
I will try when I have some time, but I don't know if it's possible without huge changes in the GUI system.
It's not a priority right now
Posted: Mon Sep 01, 2008 11:09 pm
by le_magn
Hi Gnozal, if i add hyperlink gadget and activate purecolor for this gadget, the background color remain white and not transparent, i have to change manual from source code, thank's for your work, bye.
p.s. sorry for my english.
Posted: Tue Sep 02, 2008 6:25 am
by ozzie
gnozal wrote:pebo wrote:I think i have found a little Bug in PureForm:
When i use the Menu "Translate from Source", then will be the line with:
Code: Select all
GadgetToolTip(#ButtonGadget, "Sample Tool-Text")
not translated.
It's not a bug, it's an incomplete feature

The 'Translate from source' feature is incomplete, it only imports windows and gadgets (missing : statusbar / menu / etc...) ...
I may improve it a bit, but it will never be perfect, as PureFORM handles some data it's own way (for example, some enumerations are not saved, they are generated in realtime).
(Above quote is from a Feb 2008 posting.)
Many thanks, gnozal, for the excellent PureFORM and jaPBe products. I'd just like to record another 'vote' for having GadgetToolTips translated from source. :roll: I'm converting a VB project to PB (using a modified version of VB2PB.pb) and have many tooltips.
Posted: Tue Sep 02, 2008 11:05 am
by PresFox
AMAZING program!
Posted: Thu Sep 04, 2008 9:27 pm
by Micko
hi gnozal, i try to use spplitterGadget in PureForm but couldn't make it work.
Posted: Fri Sep 05, 2008 1:10 pm
by gnozal
Micko wrote:hi gnozal, i try to use spplitterGadget in PureForm but couldn't make it work.
Did you try the example from the manual :
http://freenet-homepage.de/gnozal/PureF ... Manual.htm ?