-
File Added: not_disabled_controls_fix+minimal_sample.diff.
2007-12-28 19:54:54 UTC in wxWidgets
-
The other day I ran across a situation: I had set up an accelerator table with keyboard shortcuts for controls on my form. Sometimes these controls could be disabled... but using the accelerator keys _always_ triggered the control's event handler: even if the control should be disabled in that situation!!!
Attached are two patches, made against 2.9: one shows the issue in a minimal sample...
2007-12-28 19:54:01 UTC in wxWidgets
-
Stefan,
Are key codes supposed to tell you what physical key the user has pressed (for example, the third key left of the delete/backspace key - being the subtract key on the US layout, and being something totally different on non-us+query keyboards), or are they supposed to tell the programmer what ASCII character the user tried to enter ("-" in the case above)?
For example, Robin Dunn in...
2007-10-03 16:41:51 UTC in wxWidgets
-
From wx-dev March 04, 2007, message-id r02010500-1048-247D776ACA6B11DBA25E001451DC36C2@[10.0.1.6]
-----------------
My wxMac application needs a way to specify the size the (top level) window should zoom to. On the Mac a top level window has two zoom states: the most recent size the user selected, and the size the application "suggests" for that window (the window's ideal size).
Right now...
2007-09-19 19:02:16 UTC in wxWidgets
-
The Key Code Identifier list shows several key codes that wxMac doesn't support. This can be verified by going into the Keyboard sample and typing the following keys:
* the subtract key on the keyboard
* the plus key on the keyboard
* the divide key on the keyboard
* the decimal (.) key on the keyboard
* the multiply key (*) on the keyboard
These keys show up as their values, instead...
2007-09-06 01:21:07 UTC in wxWidgets
-
There's an off by one error for getting the F13-F15 glyph for menu shortcuts.
In UMASetMenuItemShortcut(...):
SInt16 glyph = 0 ;
SInt16 macKey = key ;
if ( key >= WXK_F1 && key
2007-06-21 16:42:28 UTC in wxWidgets
-
Logged In: YES
user_id=304442
ok. check out the new version of the patch with changes to
avoid duplicating data. Thanks Kevin!
2006-11-01 03:52:54 UTC in wxWidgets
-
Logged In: YES
user_id=304442
>What is wrong with using the existing SetRange and GetMin
/GetMax
Yes, that's a better idea, especially if the programmer
changes these values after creation.
>This patch would also not allow inputting using scientific
notation (i.e. using an e)
Ahh! I was wondering why you were able to type an "e" into
the field! How do I take input like this and...
2006-10-25 19:18:22 UTC in wxWidgets
-
The current implimentation of wxSpinCtrl does not check
the text control part of the spin control well enough
for "stupid user input"
Two cases:
#1: User inputs a non-numeric character
#2: User inputs a number larger or smaller than the
max or min range (respectively) of the control
The patch includes changes to
src/mac/carbon/spinctrl.cpp and a modification of the
minimal...
2006-10-24 23:40:59 UTC in wxWidgets
-
Logged In: YES
user_id=304442
The problem didn't happen with any wx code, but in my user code.
If you don't want to use the patch, could you at least:
a) put a #warning in wxMacFilename2FSSpec that says
FSSpecs are depreciated
b) Do some error checking of the result from
wxMacPathToFSRef (which does return the OSStatus) and
throw up a wxASSERT_MSG (or wxLogError()......
2006-09-25 17:14:47 UTC in wxWidgets