Plum, Jason wrote:
While I have not gone in to seek out the GetDialogBaseUnits I do know
that most of the units we work with in Win32::GUI are pixels,
Ah that helps. I guess nearly all window locations, apart from top-level
windows, are given in client coordinates. That is relative to the upper left
corner of the parent window.
moreover that between dialog buttons/checkboxes it is not *required*, but
I would suggest 1-2px minimum for clarity
Ah, I'll keep this in mind. But pixels as such are resolution dependent so
should I select between 1, 2 or 4 pixels based on the current resolution?
Not that it would matter that much, I reckon I could always use 2 pixels.
of the resizer code provided within the Loft/XMLBuilder or the
Win32::GUI::Resizer module.
Oh ok. can I get the resizer using PPM directly? The Active State
repositories seem not to have it.
As a special note: be sure to set the tab order when creating the contents
of your dialog considering its
potential uses.
I guess I would have to insert controls in the desired tab ordre, too, in
order for it to make sense. Leaving out something in the tab order is very
annoying so that's sure one of the bugs I'll catch first, if it should
strike me. I'm mostly using the keyboard so not being able to tab to some
control is a dier mistake. Especially in screen readers that don't provide a
virtual focus, such as Narrator.
--
With kind regards Veli-Pekka Tätilä ([EMAIL PROTECTED])
Accessibility, game music, synthesizers and programming:
http://www.student.oulu.fi/~vtatila/
