Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Plugins development => Topic started by: mandrav on November 17, 2005, 12:17:25 pm
-
...with how far wxSmith has come :shock: :shock: :shock: :shock: :shock: :shock:
Byo and cyberkoa you have done a great, let me emphasize that, GREAT JOB guys :D :D :D
I 'll also take this opportunity and suggest to all plugin developers to use wxSmith if possible. It's a shame such piece of work isn't more widely used :lol:
Just speechless...
-
We're just doing our job boss :D. But we appreciate Your opinion ;)
And there's still lot to do, so I'd better get back to work :)
-
the Toolbar to the right and the new Quick-Properties panel are great !
many many thanks too for this great tool !!!
-
just want to clearify , again :lol: , 95% or above of the work is done by byo, I am just helping those simple coding because lack of experience in C++ & wxwidgets , all credits should go to him . Still struggling to understand the core engine of wxSmith because the progress is too fast :shock: , in the starting stage still can catch up but now .. :oops:
especially the event handling of the windowseditor after the resize , undo feature added ..
-
Yes, it is AMAZING!!! (just finished tutorial BTW.) Absolutly great. Awesome job.
(btw, does CVS version support more widgets? i'm is especially interested in "property tree" widget (same as what wxSmith uses) and opengl canvas. More events (mouseover and other blabla) would be good too. But of course i can add them manually without problem so it is not really that important)
-
I want to attach my thanks too. wxSmith was the only thing I missed in C::B. I previously used devcpp, but 6 month ago I switched to C::B (thanks to all developers). But for widget design I had to use still devcpp and simillar tools - and it was little annoying. Now I am playing with wxSmith - and : IT IS GREAT. It's much better than anything I previously used (really).
I don't know where I have to post bugs. So I do it here. In .h file is one extra "#endif" (right after //(*Headers section). I am using CVS build "Codeblocks CVS20051124.7z".
And I am missing wxListCtrl widget in wxSmith toolbar.
Once again GOOD JOB.
-
Thx for your opinions ;) They seem to be to good :)
Ok, I have to confess that I've focused on stability and features so much that I've forgot that there are some missing widgets :oops:.
Of course it should be added, but standard ones (which may be found inside wx documentation, like wxGLCanvas and wxListCtrl) will have bigger priority than external ones (like property grid).
But there's nothing against adding it in future :). wxSmith is yet partially prepared for this :).
About additional event handlers (like mouse handling etc) - the problem is that wxWidgets doesn't directly support them. But I think that adding this is not impossible. I was thinking about it already and I have to do some tests before. But unfortunately it won't be available before 1.0 final.
And If You have found any bug, the best way is to send it to bug reporting system, in the C::B main page there are links in menu pointing directly to reporting tools :). Just select wxSmith somewhere in bug category and it will soon be reported to me and there's no way I could miss that ;) same with required features (good example - missing widgets :) ).
I've already found #endif bug, it should be available soon in cvs :)
And thx, cyberkoa, You've reminded me that I should write some doc with technical description of wxSmith ;).
Hmm, and maybe simplify the code :lol:
-
hope this is a correct spot to drop the question.
I've created dialog, containing a listbox, and 2 buttons below it with wxSmith.
The dialog is resizable. But how do I specify in wxSmith to get those resize lines in the bottom right corner (3 little diagonal lines ), don't know the correct terminology.
Second : Can I specify in wxSmith that the listbox should adjust to the longest entry (althoug I have second thoughts if such an approach is good, since when there's a very long entry the dialog might start to look very ugly ??) ??
Thanks,
Lieven
-
hope this is a correct spot to drop the question.
I've created dialog, containing a listbox, and 2 buttons below it with wxSmith.
The dialog is resizable. But how do I specify in wxSmith to get those resize lines in the bottom right corner (3 little diagonal lines ), don't know the correct terminology.
I have tested a few option it seems does not work , maybe is not supported by wxwidgets yet .. :? ?
Second : Can I specify in wxSmith that the listbox should adjust to the longest entry (althoug I have second thoughts if such an approach is good, since when there's a very long entry the dialog might start to look very ugly ??) ??
If you mean the listbox is auto resize at the design time , it should be expand style which will expand itself to the longest size .
If you mean resize when you resize the dialog at run time , I am afraid it is not yet supported in wxSmith :( , instead you can read the topic wxLayoutAlgorithm in the wxwidgets help file
-
The dialog is resizable. But how do I specify in wxSmith to get those resize lines in the bottom right corner (3 little diagonal lines ), don't know the correct terminology.
Try adding StatusBar:
in constructor, right after wxSmith-generated code add line
It worked for me :)
-
Well, it always was that way in any (at least windows) application.
-
The dialog is resizable. But how do I specify in wxSmith to get those resize lines in the bottom right corner (3 little diagonal lines ), don't know the correct terminology.
Try adding StatusBar:
in constructor, right after wxSmith-generated code add line
It worked for me :)
oic , I seldom work on windows programming :oops:
-
Thanks, the 3 lines are there now, but one question qnd 1 problem:
Question :
- is it my responsibility to delete it in the destructor (I have seens that for example when you create a wxMenu, new created' when you hand it over, you don't touch it anymore, certainly not delete it.So what's the case here ?
Problem:
that status bar remains at it original position , though when I enlarge the dialog, the dialog grows but that status bar is still in the starter position, so ending up in the middle of my enlarged dialog.
Seems my knowledge of wx is still way too low. :-(
kind regards,
Lieven
-
um, try adding an OnResize (or OnSize whatever) event handler that resizes the status bar whenever the window is resized...
That might work. But then again, i haven't done anything like that in a while.
-
Problem:
that status bar remains at it original position , though when I enlarge the dialog, the dialog grows but that status bar is still in the starter position, so ending up in the middle of my enlarged dialog.
Seems my knowledge of wx is still way too low. :-(
What wx version do You use ? I've noticed that also sometimes when You resize dialog, items does not reposition and resize, juzt like there was no sizer. So maybe it's wxWidgets bug (did they forget to handle size events or sth ?). I'm using wx 2.6.2 and I don't remember that this happened in ealier version.
And about memory managment - wxWidgets usually automatically handles object destruction and wxStatusBar bar should be deleted automatically
-
wx 2.6.2
-
I'll try to compile wx 2.6.1 and see the result :)