<li><a href="#shortcutproblem">Why are menu hotkeys or shortcuts not working in my application?</a></li>
<li><a href="#regconfig">Why can I not write to the HKLM part of the registry with wxRegConfig?</a></li>
<li><a href="#access">Is MS Active Accessibility supported?</a></li>
<li><a href="#shortcutproblem">Why are menu hotkeys or shortcuts not working in my application?</a></li>
<li><a href="#regconfig">Why can I not write to the HKLM part of the registry with wxRegConfig?</a></li>
<li><a href="#access">Is MS Active Accessibility supported?</a></li>
As of wxWidgets 2.1, there is a new system written by Vadim Zeitlin, that
generates the makefiles from templates using tmake.<P>
As of wxWidgets 2.1, there is a new system written by Vadim Zeitlin, that
generates the makefiles from templates using tmake.<P>
and are quite simple. They do contain some Perl code, but my Perl is
primitive (very C like) so it should be possible for anybody to make
trivial modifications to it (I hope that only trivial modifications
and are quite simple. They do contain some Perl code, but my Perl is
primitive (very C like) so it should be possible for anybody to make
trivial modifications to it (I hope that only trivial modifications
in the cvs, so you can always retrieve them and compare the new ones,
this will make it easier to solve the problems you might have.<P>
in the cvs, so you can always retrieve them and compare the new ones,
this will make it easier to solve the problems you might have.<P>
Currently this is not possible because the wxConfig family of classes is
supposed to deal with per-user application configuration data, and HKLM is
Currently this is not possible because the wxConfig family of classes is
supposed to deal with per-user application configuration data, and HKLM is
only installers should write to HKLM. This is still a point debated by the
wxWidgets developers. There are at least two ways to work around it if you really
need to write to HKLM.<P>
only installers should write to HKLM. This is still a point debated by the
wxWidgets developers. There are at least two ways to work around it if you really
need to write to HKLM.<P>
If you have downloaded the wxWidgets sources from the cvs using a Unix cvs
client or downloaded a daily snapshot in <tt>.tar.gz</tt> format, it is likely
If you have downloaded the wxWidgets sources from the cvs using a Unix cvs
client or downloaded a daily snapshot in <tt>.tar.gz</tt> format, it is likely
project. Visual C++ provides static or dynamic and multithread safe or not
versions of CRT for each of debug and release builds, for a total of 8
libraries. You can choose among them by going to the "Code generation"
project. Visual C++ provides static or dynamic and multithread safe or not
versions of CRT for each of debug and release builds, for a total of 8
libraries. You can choose among them by going to the "Code generation"
<p>
To avoid problems, you <strong>must</strong> use the same one for all
components of your project. wxWindows uses multithread safe DLL version of the
<p>
To avoid problems, you <strong>must</strong> use the same one for all
components of your project. wxWindows uses multithread safe DLL version of the
If you get errors when including Microsoft DirectShow or DirectDraw headers,
the following message from Peter Whaite could help:
If you get errors when including Microsoft DirectShow or DirectDraw headers,
the following message from Peter Whaite could help:
> This causes compilation errors within DirectShow:
>
> wxutil.h(125) : error C2065: 'EXECUTE_ASSERT' : undeclared identifier
> This causes compilation errors within DirectShow:
>
> wxutil.h(125) : error C2065: 'EXECUTE_ASSERT' : undeclared identifier
is defined, then wxdebug.h doesn't get included, and the assert macros
don't get defined. You have to #undef __WXDEBUG__ before including the
directshow baseclass's <streams.h>.
is defined, then wxdebug.h doesn't get included, and the assert macros
don't get defined. You have to #undef __WXDEBUG__ before including the
directshow baseclass's <streams.h>.