Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
New wxSmith: Testing
bugmenot:
Please put back in the popup showing when that the wxsmith version is expreimental and not for production purpose. One knew the moment one started Code Blocks that the extension was correctly installed. ;)
Bugs:
- When selecting a non wxsmith tab in the editor (such as for example a *.cpp file) then going into the resource tree and double clicking on a frame will bring the *.wxs to the front in the editor. However this does not work if you double click any of the sub widgets of a frame such as for example a button.
- When deleting the last subwidget of a box sizer the sub widget is deselected in both resource tree and preview window. Then it is deleted. Now nothing is selected in the preview window. In the resource tree the sizer gets a different background color (However a third one different from not selected and explicitly selected). Clicking on the sizer in the resource tree will make the back color change to "selected" in the tree but it will not be selected in the preview. It is not possible to add any widgets to the sizer. The solution is to either select the sizer in the preview or select something different in the tree and then select sizer again in the tree.
- In the property tab the new font element is simpler to use in my opinion than the old. However there is a bug : The font property is mad up of a tree : root with a name that resumes the settings. 2 childes one being a check box defining if a non default font should be used an another sub tree with the non default font details. The problem is that the name of the root element is editable. Editing it wont hurt as it is always automatically reset to the previews state but perhaps it might be better to make it non editable. Also if the default font is used then it might be a better idea to change the whole description to "default font" instead of "FALSE [... a lot of not used stuff...]".
- There's a probably hard to solve problem with the bitmap buttons (or any bitmap resource) in combination with the MinGW compiler and non English Windows versions (probably also non English Linux but didn't try). Files or path may contain non standard characters such as "èéäößê". The code is generated correctly. However it wont compile with the following error:
--- Quote ---converting to execution character set: Illegal byte sequence
--- End quote ---
Probably only 7bit ANSI characters are allowed in string literals but I haven't tested it.
- When a wxBitmap widget with a bigger image than the working area is created or moved the preview window is not correctly updated when scrolled. This does not happen if the widget hasn't been recently changed.
- wxSplitterWindow also doesn't always correctly distribute its client area between its childs:
I don't know under which circumstances this happens however I could produce it fairly often unwillingly so you should be able to reproduce it by playing around with the control. Also I think that wxSplitterWindow is more a sizer than a control so I'd place it under the Layout tab with all the other sizers.
- Under Windows when moving another window of another program over the preview window then it's always completely updated and flashes quiet a bit. Nothing serious but you might consider limiting the redraws per second.
--- Quote ---Bug with "EM != NULL" assertion - I've never got this so I couldn't find the reason of this failure
--- End quote ---
I can't reproduce it either with the new version. Probably it was caused by the same code which caused the fragments.
--- Quote ---Toggling "Is Member" and changing few other properties still cause editor to refresh (it would require some bigger changes in property system so maybe in future). Since there's no blinkink bug, it should not be frustrating
--- End quote ---
No it's not frustrating at all. Just wanted to point it out. ;)
--- Quote ---Problem with headers for handler functions - this will be quite hard to fix (need to parse handlers list, check what headers are required for handler arguments). Fortunately as long as pch is used, absent headers are no problem
--- End quote ---
I think you didn't understand what I suggested. You have for example the following code:
--- Code: ---//(*Headers(NewFrame)
#include <wx/textctrl.h>
#include <wx/button.h>
#include <wx/frame.h>
//*)
--- End code ---
Now I add a wxTextCtrl only handler. Meaning one which needs an event defined in that header. Now change the header code to the following:
--- Code: ---#include <wx/textctrl.h>
//(*Headers(NewFrame)
#include <wx/textctrl.h>
#include <wx/button.h>
#include <wx/frame.h>
//*)
--- End code ---
Doesn't look great but when the wxTextCtrl is removed you are left with
--- Code: ---#include <wx/textctrl.h>
//(*Headers(NewFrame)
#include <wx/button.h>
#include <wx/frame.h>
//*)
--- End code ---
and the code still compiles.
--- Quote ---Replaced previous font editor with simplified dialog (previous editor is available under advanced options)
--- End quote ---
Where are those advanced options?
Anyway the new version ran pretty stable and didn't crash.
Grom:
I tested new version of wxSmith. Still there are the same problems:
1. Components have no their names under the components icons.
2. There are no SatusBar, TooolBar and Menu and PopUp Menue. (I would say that is extremely important to have them)
3. Seems to be Byo works along.
Conclusion:
Today it is more important to have a good IDE for automatic GUI development with UML support then nice coding engine with fancy interface. With that strategy Code::Blocks project may have serious problems. Even I don't speak about rc3... (Just take a look on to wxDevCpp). CB in troubles... :(
joubertdj:
--- Quote ---Today it is more important to have a good IDE for automatic GUI development with UML support then nice coding engine with fancy interface. With that strategy Code::Blocks project may have serious problems. Even I don't speak about rc3... (Just take a look on to wxDevCpp). CB in troubles... Sad
--- End quote ---
:) Cool... so you are going to help us in writing C::B to achieve those goals?
Grom:
I will try to find time to do that. :?... I have 5 projects right now...
byo:
--- Quote from: Grom on January 15, 2007, 07:46:58 pm ---I tested new version of wxSmith. Still there are the same problems:
1. Components have no their names under the components icons.
2. There are no SatusBar, TooolBar and Menu and PopUp Menue. (I would say that is extremely important to have them)
3. Seems to be Byo works along.
--- End quote ---
Yup, but all these are new features not supported in old wxSmith also. Current roadmap is:
* Get all old wxSmith functionality
* Fix as much bugs as possible
* Merge new version into trunk and destroy/forget about/anything else to throw away ;) the old code
* Start working on new features
So, we're at the second point. And as long as wxSmith is not included inside nightlies, it won't have many new things.
And the fact that I'm working alone (I hope I've understood you correctly ;)) is nothing new to me and to wxSmith from the very beginning of the code. But I've thought about other workers during rewrite and hopefully it will be much easier to work with other people here (I mean in new wxSmith framework code) :)
--- Quote --- Conclusion:
Today it is more important to have a good IDE for automatic GUI development with UML support then nice coding engine with fancy interface. With that strategy Code::Blocks project may have serious problems. Even I don't speak about rc3... (Just take a look on to wxDevCpp). CB in troubles... :(
--- End quote ---
Ok, maybe it's not objective point of view, but I think that wxSmith is not so important for C::B as it may look like. It may be replaced with other tools (like wxFormBuilder, wxGlade and many others). It's not so hard to make C::B cooperate with them, and the time needed to learn how to use these tools shuld be no more than few hours.
And there's no UML plugin worked on right now AFAIK :(.
So maybe C::B is in trouble but this is open-source. We do not lose any money, we do not lose jobs if we fail. We simply give you all we can. And if it's not enough, so... we do not keep anyone tighed to this IDE.
Ok, but Grom some important issue. So here's my question:
Is there anyone interested in helping me with wxSmith?
C++ and any knowledge about wxWidgets appreciated :)
If someone is interested in making some graphic for wxSmith
(mostly icons, buttons etc) I would also be grateful for this
kind of help :)
Ok, maybe few answers to bugemnot's last bug report:
I haven't removed warning message, it shuold be displayed as usual (or maybe I've messed something up, but I got this message on my PC).
Only selecting resource item in resource browser causes editor to be switched.
But I may change it.
Problem with invalid code is known to me but it may require some hard work to fix - sometimes it's caused by problems with encoding in C::B. Try switching encoding in options, maybe that will help.
The problem with header still remains. Currently I don't see easy solution (you one is simple and suffixient but hard to implement). Currently I'll leave this bug open.
Regards
BYO
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version