My thinking on this is pretty straight forward. If an unexpected run
time condition occurs, use one of the wx debugging macros (wxASSERT,
wxCHECK, wxCHECK_RET, etc.). If you just want to look at internal state
information while the application is running, use wxLogTrace and turn
the output on/off as required. Does this debugging output not fall
under either of those categories?
On 4/14/2019 10:57 PM, Seth Hillbrand wrote:
> I'd second that approach.
>
My thinking on this is pretty straight forward. If an unexpected run
time condition occurs, use one of the wx debugging macros (wxASSERT,
wxCHECK, wxCHECK_RET, etc.). If you just want to look at internal state
information while the application is running, use wxLogTrace and turn
the output on/off as required. Does this debugging output not fall
under either of those categories?
On 4/14/2019 10:57 PM, Seth Hillbrand wrote:
> I'd second that approach.
>