wxSmith - tutorial

[wxSchmidt]

Hi, im new to wxsmith, but it seems to be a powerful GUI-creation-tool.
Are there any other tutorials than "HELLO WORLD" available?

[byo]

Hi, im new to wxsmith, but it seems to be a powerful GUI-creation-tool.
Are there any other tutorials than "HELLO WORLD" available?

Currently AFAIK there are no other tutorials, I could write some but don't have enough time . Maybe you could add something there if you figure out how wxSmith works I could help in case of problems

Regards
  BYO

[Adam01]

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?

[Jenna]

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?

If you chose the button in the wxs-tab you see the propertygrid in the resources-tab in the manager.
Between the resouces-tree of your project(s) and the propertygrid belonging to the active element, there are two buttons/icons.
One is activated (the one that looks like a list).
Click on the one with the two curly braces and you can assign an event to the button by chosing "Add new Handler" from the dropdownlist on the right.

[Adam01]

Thanks, I worked that out just after I posted that question.
Does wx have its own threading system?, so I could multi-thread gauges and other animations.

[Adam01]

Also, using wxFileSelector, how can I use ofstream to open the return value?
It is a wxString, but is there anyway to convert it to a char?

[byo]

You can use such scheme to convert wxString into const char*:

Code Select Expand

wxString someString;
const char* chars = someString.mb_str(wxConvLocal);

This may work in many cases but will probably cause big problems when some local characters are used in the path due to different character encodings.

Did you try to use wxFileStream class instead? I'm not familiar with it so I can not tell whether it works like standard iostreams.

Regards
   BYO

[Master]

hello , and sorry i just figured it out that i shouldnt have posted here ! ,

many tanx MortenMacFly

[MortenMacFly]

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.

[Master]

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 .

[Grom]

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.

Edit: [REMOVED NON ENGLISH CONTENT] :lol: :lol: :lol:

[Fex]

I'm working my way through the wxsmith tutorials. They are really good 

I have not worked with wxwidgets before but I do have a fair bit of programming experiance. I have a question about tutorial 4

http://wiki.codeblocks.org/index.php?title=WxSmith_tutorial:_Working_with_multiple_resources

The code says

Code Select Expand

void Tutorial_4Frame::OnButton3Click(wxCommandEvent& event)
{
    FirstFrame* frm = new FirstFrame(this);
    frm->Show();
}


Shouldn't there be a

Code Select Expand

delete frm;

in there somewhere to ensure no memory leaks? Or does it automatically handle them somehow?

Fex.

[Pecan]

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), 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

[Fex]

Thanks Pecan 

[ollydbg]

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), 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

This is a good tutorials on wxWidgets creation and destroying! thanks for your explanation.