Charles Hartman wrote:
Thanks -- and to Alex, too -- I hadn't thought of grouping the check-
boxes. I'm first going to try a simpler more permissive approach
and see how the user-experience feels, but if that's not satisfactory
I'll do the second group.
That's (kind of) why I suggested a
Thanks -- and to Alex, too -- I hadn't thought of grouping the
check- boxes. I'm first going to try a simpler more permissive
approach and see how the user-experience feels, but if that's not
satisfactory I'll do the second group.
That's (kind of) why I suggested a global rather than
Sarah Reichelt wrote:
I find it frustrating to come across a disabled button and not be able
to see why it is disabled. In one application I am developing, I have
adopted the following strategy for screens where a lot of data must be
entered before proceeding: I put an invisible button
Hi Richard,
1. I suppose that the development team was for this option (no
tooltips on disabled controls) since the contrary (as for me I would
like it too) would mean having to script all tooltips dynamically at
mouseEnter (what I do every day to such an extend that I wrote a
tutorial
Eric Chatonet wrote:
Le 5 août 05 à 09:01, Richard Gaskin a écrit :
Tooltips could accomodate this as well, if only they worked when the
control is disabled.
Another reason to vote for BZ#197:
http://support.runrev.com/bugdatabase/show_bug.cgi?id=197
1. I suppose that the development
That's brilliant!
Le 5 août 05 à 09:31, Richard Gaskin a écrit :
Perhaps the simplest solution would be to have a new
disabledTooltip property.
I just updated the BZ report to suggest that.
Best Regards from Paris,
Eric Chatonet.
I've got a complicated dialog (too complicated! but it will look
simple to the user I think), and I can't figure out how best to
design it to deal with the messaging system.
This card in the dialog has a column of half a dozen check-boxes, and
a column of a dozen or so radio buttons in a
When you say wait, what do you really mean? Do you mean you want to
force the user to click on a radio button before doing anything else?
Or do you literally mean you want to force a delay of some sort?
Assuming the former, one easy way to do this would be to put the
checkboxes in a group
Charles Hartman wrote:
I've got a complicated dialog (too complicated! but it will look
simple to the user I think), and I can't figure out how best to
design it to deal with the messaging system.
This card in the dialog has a column of half a dozen check-boxes, and
a column of a dozen
Thanks -- and to Alex, too -- I hadn't thought of grouping the check-
boxes. I'm first going to try a simpler more permissive approach
and see how the user-experience feels, but if that's not satisfactory
I'll do the second group.
But either way, there's something I still don't quite
Ah! Never mind -- I just found the target() function.
Charles
On Aug 4, 2005, at 10:23 PM, Charles Hartman wrote:
Thanks -- and to Alex, too -- I hadn't thought of grouping the
check-boxes. I'm first going to try a simpler more permissive
approach and see how the user-experience feels,
Charles,
Just a guess, but did you look at the Target?
That way you could put a mouseUp handler in the group and use either and
if-then or a menuPick conditional structure in conjunction with the
Target, e.g.,
pseudocode:
on mouseUp -- at the group level
if the Target is whatever
...
end
Rats. Could've saved myself some typing ;-)
Judy
On Thu, 4 Aug 2005, Charles Hartman wrote:
Ah! Never mind -- I just found the target() function.
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe,
Charles,
You can also put a mouseUp handler in a group:
on mouseUp
put the hiliteButton of me into tButtonNumber
-- OR
put the hilitedButtonName of me into tButtonName
- OR
put the hilitedButtonID of me into tButtonID
end mouseUp
___
14 matches
Mail list logo
