Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

wxSmith generated typecast for handler functions

(1/2) > >>

Alpha:
According to bug 19334, the way wxSmith is currently generating casts causes errors with MSVC.  From past reading of wxWidgets documentation, the preferred method is with their builtin macros such as: wxCommandEventHandler() .

In the attached patch, I have implemented this change.  However, I am unfamiliar with wxSmith code, so I would appreciate if someone else could comment on this.

Alpha:
I will commit this coming weekend, if no comments.

MortenMacFly:
So far I tried several wxsnith projects without error.what's missing is a customised control... How many wxsmith projects did you try?

Alpha:
I did it on a few personal/test projects, and on a sampling of dialogues in C::B.  So, not exactly a thorough test.
I rarely use advanced features of wxSmith... what do you mean by customized control?

MortenMacFly:

--- Quote from: Alpha on February 17, 2015, 11:07:26 pm ---I did it on a few personal/test projects, and on a sampling of dialogues in C::B.  So, not exactly a thorough test.
I rarely use advanced features of wxSmith... what do you mean by customized control?

--- End quote ---
Well you can embed customised controls (i.e. controls not supported by wxSmith) into a wxSmith layout.
Additionally did you try it on the wxSmith Demo that hold all controls? I am not sure (however), if these controls have handlers connected though. but another test would be to setup a dummy for all handlers at least on standard controls like wxTextBox etc. to see if it works correct in all cases.

Navigation

[0] Message Index

[#] Next page