Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
wxSmith development
mandrav:
Hey byo,
Your thread already reached the third page. Maybe I should create a different forum for wxSmith? It seems like it's gonna be busy :mrgreen:
Yiannis.
byo:
--- Quote from: mandrav ---Your thread already reached the third page. Maybe I should create a different forum for wxSmith? It seems like it's gonna be busy :mrgreen:
--- End quote ---
Hmm, I'm just wondering why RAD tool is such popular. New forum ? Maybe after reaching 4th or 5th page ;) will se how long it would take to reach that - if would be reached fast, this would mean that new forum is a must ;)
--- Quote ---This must have to do with some events processed by wxSmith plugin, not being skipped (event.Skip()) so that they can be processed by other plugins too.
I mentioned it before and byo said he would look into it.
--- End quote ---
Yep, already fixed, in CVS but... i frorgot to add some files to repository :oops: so You may not be able to compile :( Just wait a minute and it will be there
rickg22:
This ought to be in the readme. Whenever you create a new file, add it to CVS immediately ;-)
cyberkoa:
--- Quote from: cyberkoa ---
My question is ,what is the purpose of having the flag VarNotStored in the struct wxsWidgetBaseParams.
--- End quote ---
I would like wxSmith to create dialogs and other resources in two ways - first one is to create XRC file and then to automatically manage code loading / event handling etc. Second way is to manage code wchich would create dialog without loading xrc. In this way each widget must have it's variable (just pointer to it's class) - it could be stored as a member of dialog's class (VarNotStored=false) or could be created locally inside funnction building dialog (VarNotStored=true) - using first one means that You want to use widget somewhere in class - read it's content or change it so it's good for edit fields check boxes etc. Second one means that You don't want this widget to be stored inside edialog's class - good for static widgets which won't change (and won't mess dialog's declaration).
Hmm, I hope I've explained that :oops: :)[/quote]
Thx,understood. The flag indicate whether the widget is static widget (keep in xrc) or dynamics created using C++ code . Hmm ,this is important in code generation.
Still studying the source code.. shall ask question when see something not understand .. thx
cyberkoa:
--- Quote ---
--- Quote from: cyberkoa ---
--- Quote from: cyberkoa ---
My question is ,what is the purpose of having the flag VarNotStored in the struct wxsWidgetBaseParams.
--- End quote ---
I would like wxSmith to create dialogs and other resources in two ways - first one is to create XRC file and then to automatically manage code loading / event handling etc. Second way is to manage code wchich would create dialog without loading xrc. In this way each widget must have it's variable (just pointer to it's class) - it could be stored as a member of dialog's class (VarNotStored=false) or could be created locally inside funnction building dialog (VarNotStored=true) - using first one means that You want to use widget somewhere in class - read it's content or change it so it's good for edit fields check boxes etc. Second one means that You don't want this widget to be stored inside edialog's class - good for static widgets which won't change (and won't mess dialog's declaration).
Hmm, I hope I've explained that :oops: :)
--- End quote ---
Thx,understood. The flag indicate whether the widget is static widget (keep in xrc) or dynamics created using C++ code . Hmm ,this is important in code generation.
Still studying the source code.. shall ask question when see something not understand .. thx :D
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version