To BYO,
you're a legend. I downloaded the latest CVS of Code::Blocks (after playing around with R1C2 for a while) and the whole team deserves mountains of credit for their efforts. However I am absolutely smitten with wxSmith. I love the new interface and the relocation (and nice icons for placement ops) to the bottom of the editor window. Sensational. I've really looked around at the other open source offerings in the IDE genre and Code::Blocks totally rocks the opposition. Keep up the great work. I can see from recent posts that you have really attempted to implement suggested enhancements in a logical and user friendly way. So in this spirit I'll make a small suggestion, though I am positive you will have it already on your TODO list. The ability to define further controls (and eventually custom controls) would be really nice. I guess this would be best after you've got things to a really stable state and you are happy with wxSmith in it's current form. Keep rockin, and when I've played with it more extensively I'll get back with further feedback.
The Falcon.
Waiting For Your suggestions and bug reportsa suggestion: maybe it would be a good idea to consider, to make wxSmith also available via separate package on C::B SF's project page, with its own, independent release cycle? The amount of changes being made to this plugin... you know... it just stuns. :P
I've just seen quite latest wxSmith (thanks to binaries (http://paginas.terra.com.br/informatica/mauricio/codeblocks/) provided by therion), and I just cannot left what I've seen uncommented...
byo: it occurs (almost) all the time when you drag a component
I found one very obvious black background screen problem in wxNotebook when I do the style update , I hv tried to debug but it seems like quite complicated to me.
Takeshi Miya: Can You describe Black screen more precisely (the most important thing is when it does occur). I noticed this behaviour but have too few informations about that. Maybe some bug report ;)
BTW. Can anyone help me with Linux version ? I really have no Idea why it don't want to load :( And Squizz: I've divided by zero and still have exceptions ;)I have the same problem in Ubuntu 5.10 breezy, the profiler plugins also does not loaded properly.
question : what do the top 3 buttons on the right hand side do (tested with snapshot build of CB of 16 november 2005) ? Would be nice if there are also tooltips for those buttons.
Thanks,
Lieven
and the panels are going to be managed by wxDockIt?
Please advise, for future reference, whether posting this type of stuff here is appropriate or is formal bug reporting the more desired option?
1. When using the preview facility after only defining a panel and a sizer the minimal preview dialog is displayed. The normal 'x' close button doesn't seem to respond. You can still close if you right click on the header and select 'close', so it's a minor annoyance but I suppose the 'x' close button should really work.
2. The hotkey/accelerator key assignments are not displayed in the preview. i.e. No underlines etc. This seems a bit weird as you can happily play with a combo box and buttons etc. in preview but the first time I saw the buttons I thought I'd forgotten to do the old '&' insertion. I hadn't, it just wasn't reflected in the preview.
3. Subsequent to the already identified 'Black Screen Issue' I noticed that this also occurs when you use the border size spin control in the size options panel. It doesn't do it for ever click, just after a few, and it isn't persistent as it usually returns to normal on clicking up or down to the next value.
4. Another one that may be related to the above (but it's really minor) and may help to lead to the source of the problem is that the size anchor tabs (the little black size tabs around the selected control/widget) flicker madly when you have something selected in wxSmith and use the C::B main menu. It doesn't happen for all menus and I struggled to get a consistent respnse but it does happen if you activate a menu then sweep across the menu titles.
5. When using the properties/events pane to define an event handler you are presented with a small dialog to define the event name. If you choose cancel here, instead of defining a name and pressing OK, the event pane does not re-paint correctly. It will re-paint if you go to the properties tab and then return, but I guess that's not really what you intend.
6. I have a more interesting issue with hidden controls/widgets and their usage with wxSmith but I'm not sure if it's a wxSmith issue. It may be related to wxWidgets, and how they work with sizers (I am reasonably new to both wxWidgets and C::B but ancient as far as C++ and RAD GUI interfaces go) so maybe I just need to be pointed at some documentation on how to manipulate hidden widgets in relation to sizers etc. I notice with interest that when you use the properties window to set the HIDDEN property in wxSmith the selected widget is moved to the top of the display and the container/sizer is resized. Also, when hidden, the widget still appears in the preview facility as if it was still visible. Hmmm. this might be a tad confusing to some. Anyway I tried shifting the widget->hide() code around in the source (and re-compile) and did get it to appear in locations other than at the top of the dialog but as yet I have'nt been able to get it to work properly. Most likely it's a product of my relative inexperience with wxWidgets but any light you can shed on this would be helpful, or is it something I should forward to the wxWidgets forum? Have you experienced any difficulties with this issue in the wxSmith implementation?
Anyway that's it for now, hope some of this helps, and keep up the great work,,,,
PS: Love the widget multi-select property setting. Sort of didn't ecpect it at this stage but there it is, well done.
What happened to the tutorial. I can't find it. It doesn't appear in the wiki any more.
I can't find it. It doesn't appear in the wiki any more.Main page -> "Developing for Code::Blocks" (in table of contents) -> "wxSmith Tutorial & Pointers"
Hi, im new to wxsmith, but it seems to be a powerful GUI-creation-tool.
Are there any other tutorials than "HELLO WORLD" available? :D 8)
Does anyone know how to make a function, called when a button is clicked?
The tutorial uses frame::OnButtonClick(wxCommandEvent& event){}, but the function prototype needs to the declared first, I did that in the frame class, but still nothing happened.
Does anyone know anything about button events?
wxString someString;
const char* chars = someString.mb_str(wxConvLocal);
hello, i got some questions!:Sorry to interrupt here, but these question go far beyond the scope of our forums. Thus in fact they violate our forum rules. I suggest you ask in a programming and/or wx related forum.
tanx, edited .hello, i got some questions!:Sorry to interrupt here, but these question go far beyond the scope of our forums. Thus in fact they violate our forum rules. I suggest you ask in a programming and/or wx related forum.
hello, i got some questions!:Sorry to interrupt here, but these question go far beyond the scope of our forums. Thus in fact they violate our forum rules. I suggest you ask in a programming and/or wx related forum.
void Tutorial_4Frame::OnButton3Click(wxCommandEvent& event)
{
FirstFrame* frm = new FirstFrame(this);
frm->Show();
}
delete frm;
I learned the hard way, that if you delete a control/frame/window that is owned by wxWidgets, wxWidets will have a stroke and die.
When a wxWidgets owned frame is destroyed by wxWidgets, all its children will be destoyed automatically.
The objects you need to delete are the ones you created outside the wxWidgets knowledge, such as "myvartype* myvar = new (myOwnArray)" etc. wxWidgets doesn't know about these.
There was a good post about this by Thomas on the forum some time back(Here (http://forums.codeblocks.org/index.php/topic,2105.msg16605.html#msg16605)), but the links became obsolete. I think they were these:
http://docs.wxwidgets.org/2.8.6/wx_windowdeletionoverview.html
http://wiki.wxwidgets.org/Avoiding_Memory_Leaks
Key words: wxWidgets ownership responsibility deleting avoiding memory leaks deletion overview