still same.
This is the first time I am trying to use wxSmith, but I find it completely unusable.
I am just wondering though, are there noperfectly acceptablealternatives already? Open source or otherwise?
#include <windows.h>
int main()
{
HANDLE hTest;
int iVar;
iVar = 10;
hTest = &iVar;
return 0;
}
This is the first time I am trying to use wxSmith, but I find it completely unusable.
I have several interesting coversations with mandrav
and the conclusion:
It's hard for byo to work on the old code hunting bugs, when he created the new code for exactly this reason: to be manageable and easy to find/fix bugs.
Yes, wxSmith can crash C::B. But, at the same time, it works fine in most (simple, if you want) cases.
If it helps you, think of wxSmith as a technology preview. It's not a finished product in any way.
in the mean time I'm still waiting for my asdl connection so I can look at the newer version.
even thinking about helping out a little bit :shock:
that is, if my personal life does not get in the way. :D
cheers,
jewe
Hello, I have reported a small bug with the tooltip in debbuging session (when you put your mouse over a variable)I also noticed this.
This is the first time I am trying to use wxSmith, but I find it completely unusable.When I first used wxSmith several months back, it promptly crashed the application. Usually, if something crashes, I don't give it a second try, but for some reason I did here.
In the particular case of wxSmith, I daresay that your judgement is entirely unfair.
One thing I have not been able to fix though is that the dialog is 'pushed down' by the title bar, making the bottom 'drop off'. And I have old style (non-XP) controls. Whereas wxSmith displays a preview of the same XRC just fine.Can you add this as an bug in the wxFormBuilder issue tracker (http://issues.wxformbuilder.org). Thanks.
Are you saying this is a bug in wxFormbuilder? So what exactly is it producing that it should not? Or vice versa?I believe that the dialog should display the produced dialog the same as it is once the code is compiled and running. So yes, I think it is a bug.
I believe that the dialog should display the produced dialog the same as it is once the code is compiled and running. So yes, I think it is a bug.