Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Plugins development => Topic started by: szczepan on September 26, 2007, 03:26:27 pm
-
Long version: sorry guys/gals, but seeing a GUI builder being developed for so many years that STILL fails to update the variable name in the widget tree when the property is edited in the property sheet just makes you want to bang at your desk with your forehead, doesn't it?
Short version, just three words: model, view, controller.
-
hi. I believe you are referring to the case where after changing the variable name , and clicking on any place other than in the properties grid . If you are clicking on other properties inside the property grid , or press a tab , it will not be a problem.
I think this is because the property grid component used in wxSmith is come from wxPropertyGrid (a 3rd party component), and in your case , it will not trigger the "OnChange" event in the wxPropertyGrid, and subsequently will not trigger the "code change" in wxSmith
I think byo can give a better & detail explanation.
-
Long version: This is Open-Source, we, the maintainers, usually have nothing but simple "thank you" or "your work sucks" from users of our software. In your case it looks like the second one. So your post makes me want to bang at my desk with my forehead (actually in my case it even can't be called desk, I simply can't afford any desk yet) and AFAIK I've already fixed the issue you've described. Anyway, thanks for your opinion. If you still think it's my bug, please send bug report. You can also prepare some patch if you'll find the reason of bug.
Short version: Try to contribute yourself, it makes nice overwiew of how it looks like from my side.
Sorry, but I'm tired after long day in work, and there are still some more important bugs in wxSmith which I want to fix first. Good night.
-
Long version: sorry guys/gals, but seeing a GUI builder being developed for so many years that STILL fails to update the variable name in the widget tree when the property is edited in the property sheet just makes you want to bang at your desk with your forehead, doesn't it?
Short version, just three words: model, view, controller.
Short version, just three words: use something else
-
Short version, just three words: use something else
I do.
-
For me is a great tool, I'm developing a commercial application at my job, and I use wxSmith. It does the job and thats what matters for me. Some little inconveniences, but jey is free. You can't ask for so much. What I know is that this tool really speeds up the development of gui and thats great! :D
Is difficult to work on a full-time job and also dedicate time to another job (for free). If every people on this community stop developing then we are not going to have any of these great tools for free. So come on people you should be thankful for the existance of tools like this one and the developers working on it. Thats how our precious linux was born. :wink:
-
I tried a lot of IDE's in the last years, free and commerial's. Codeblocks is the only one, which provides the ability to develop applications under WINDOWS, LINUX and MAC in the same environment. In most cases you can even use the same project files. You can use nearly all known compilers. You can talk to the developers of the IDE and there is a great community standing for help if you are on trouble. You have to pay nothing. :D
I can't believe, that you'll find a better bid. :?
-
It works very well for me and its getting better and better...
Thanks for your great work,
Jan
-
The C::B needs in release to bring more people to help with wxSmith. At list with new components. Today there is a tool to add new components. Lot's of people will do that if you guys will make a new release.
-
We have a project that is supposed to gain lots of functionality from plugins, but it never leaves a stable base for plugins. It makes it hard to for a developer plugins.