Hi,
SOrry, I seem to be on about these quite a lot!
Sijnce my last set of troubles, I have figured these puppies out, and discovered that although they're accessible to screen reading technologies on OS X, an presumably Linux, they aren't on Windows.
Is there a "1 size fits all" solution? Or do I have to put os-specific code everywhere?
Cheers,
Chris Norman wrote:
Hi,
SOrry, I seem to be on about these quite a lot!Sijnce my last set of troubles, I have figured these puppies out, and
discovered that although they're accessible to screen reading
technologies on OS X, an presumably Linux, they aren't on Windows.Is there a "1 size fits all" solution? Or do I have to put os-specific
code everywhere?
If you need to ensure the use of native controls everywhere then yes, you'll need to have os-specific code. wxWidgets will use generic controls whenever the native widget set is not up to the job.
--
Robin Dunn
Software Craftsman
That’s great stuff, I’l get working on that then.
Thanks for the help,
On 14 Oct 2014, at 01:11, Robin Dunn <robin@alldunn.com> wrote:
Chris Norman wrote:
Hi,
SOrry, I seem to be on about these quite a lot!Sijnce my last set of troubles, I have figured these puppies out, and
discovered that although they're accessible to screen reading
technologies on OS X, an presumably Linux, they aren't on Windows.Is there a "1 size fits all" solution? Or do I have to put os-specific
code everywhere?If you need to ensure the use of native controls everywhere then yes, you'll need to have os-specific code. wxWidgets will use generic controls whenever the native widget set is not up to the job.
--
Robin Dunn
Software Craftsman
http://wxPython.org--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.