Re: Back to button basics

2006-12-11 Thread Josh Mellicker

hoverIcon is promising but has one bug:

It reset icons to the normal Icon on mouseLeave, but alas, it does  
not reset changed buttons upon leaving the card.


So, if you click a button that takes you to a different card, and  
your mouse is moving, whatever icons you are switching will stay  
stuck showing the hoverIcon.


Upon returning to the card with the buttons, it looks strange indeed!  
With some buttons showing over states.


I have sadly given up on hoverIcon and gone back to Chipp's idea of  
manually switching out icons, which works flawlessly.



The only solution I can think of, is that upon going to a different  
card, Rev has to insert code that checks all icons on the card it's  
leaving, and resets any showing the hoverIcon to the regular Icon.


Is this a Bugzillable issue?


On Dec 5, 2006, at 9:30 PM, Tereza Snyder wrote:

If I want rollover behavior, I would use the new hoverIcon property  
instead of the autoArm and armedIcon property


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Back to button basics

2006-12-11 Thread Ken Ray
On 12/11/06 12:15 PM, Josh Mellicker [EMAIL PROTECTED] wrote:

 hoverIcon is promising but has one bug:
 
 It reset icons to the normal Icon on mouseLeave, but alas, it does
 not reset changed buttons upon leaving the card.
 
 So, if you click a button that takes you to a different card, and
 your mouse is moving, whatever icons you are switching will stay
 stuck showing the hoverIcon.
 
 Upon returning to the card with the buttons, it looks strange indeed!
 With some buttons showing over states.
 
 I have sadly given up on hoverIcon and gone back to Chipp's idea of
 manually switching out icons, which works flawlessly.
 
 
 The only solution I can think of, is that upon going to a different
 card, Rev has to insert code that checks all icons on the card it's
 leaving, and resets any showing the hoverIcon to the regular Icon.
 
 Is this a Bugzillable issue?

Absolutely! And I'd recommend entering it NOW as they are working on fixing
bugs for the 2.7.5 release and it would be great to get that fixed right
away...


Ken Ray
Sons of Thunder Software, Inc.
Web site: http://www.sonsothunder.com/
Email: [EMAIL PROTECTED]


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Back to button basics

2006-12-11 Thread Josh Mellicker
Okay, I have not yet bugzilled yet, and this is not as major as other  
issues... and there is a fine workaround for now, just so everyone  
knows, I have just been working with this and if to fix the stuck  
over button problem, just set the hoverIcon to 0 (to disable it),  
set the armedIcon to the same as the icon and swap out the icon  
number manually on mouseEnter, this works perfectly.



On Dec 11, 2006, at 11:24 AM, Ken Ray wrote:


On 12/11/06 12:15 PM, Josh Mellicker [EMAIL PROTECTED] wrote:


hoverIcon is promising but has one bug:

It reset icons to the normal Icon on mouseLeave, but alas, it does
not reset changed buttons upon leaving the card.

So, if you click a button that takes you to a different card, and
your mouse is moving, whatever icons you are switching will stay
stuck showing the hoverIcon.

Upon returning to the card with the buttons, it looks strange indeed!
With some buttons showing over states.

I have sadly given up on hoverIcon and gone back to Chipp's idea of
manually switching out icons, which works flawlessly.


The only solution I can think of, is that upon going to a different
card, Rev has to insert code that checks all icons on the card it's
leaving, and resets any showing the hoverIcon to the regular Icon.

Is this a Bugzillable issue?


Absolutely! And I'd recommend entering it NOW as they are working  
on fixing
bugs for the 2.7.5 release and it would be great to get that fixed  
right

away...


Ken Ray
Sons of Thunder Software, Inc.
Web site: http://www.sonsothunder.com/
Email: [EMAIL PROTECTED]


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your  
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-revolution


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


RE: Back to button basics

2006-12-06 Thread Jan Sælid
Tereza, 

6. desember 2006 06:30, you wrote
If all the buttons do is signal a state change that will be acted on  
later, I would put the following script in the group:

Fantistical,

Not only did you help me out - you threw in some lessons too. I'm
enlightened and my head is in order. What an absolutely tremendous reply.

Big handshake,

Jan

---
Jan Selid
[EMAIL PROTECTED]


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Back to button basics

2006-12-06 Thread Tereza Snyder


On Dec 6, 2006, at 2:25 AM, Jan Sælid wrote:



6. desember 2006 06:30, you wrote

If all the buttons do is signal a state change that will be acted on
later, I would put the following script in the group:


Fantistical,

Not only did you help me out - you threw in some lessons too. I'm
enlightened and my head is in order. What an absolutely tremendous  
reply.


Big handshake,


You're welcome! Normally I'm so slow on the uptake that by the time I  
type in a reply to anyone, there are already five responses on the  
list. Last night the speedy answer guys must have been busy (or asleep).


After I sent off my reply, though, I thought of one more bit of info.  
You could avoid having the script in the group (set the hilite of  
the target to not the hilite of the target) by using checkbox  
buttons to start with, because checkboxes inherently toggle hilites.  
Therefore, set their icon properties and leave their autohilite true.  
You can deal with the button names by hiding them (set their showName  
to false) or working with their textAlign property and margins.


Glad to help,

t



--
Tereza Snyder

   Califex Software, Inc.
   www.califexsoftware.com

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Back to button basics

2006-12-05 Thread Jan Sælid
Hi folks,

I’m redesigning my buttons. it’s been a while since the last time. The
autobehaviour drives me nuts. Can someone please tell me what to turn off
and on in the following scenario:
The buttons belongs to a group. There should be no radiobehaviour. They
should all be transparent. No hilited border. Nothing. The only thing that
changes is the icon on mouseup. I use a custom on/off state like this:

On mouseup
   If the onstate of me is true
Then
Set the onstate of me to false
Else
Set the onstate of me to true
  End if
End mouseup

What I want to do is to just change the icon according to the state of
onstate property. Should I use a visited icon or a hilited icon? No matter
what I turn off or on I seem to get some additional behaviour. Like a border
or the traversal  border. I’m sorry that I have to bother you with this but
my early days of lessons is just hidden under layers of other priorities. 

Sincerely

Jan Selid

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Back to button basics

2006-12-05 Thread Tereza Snyder


On Dec 5, 2006, at 9:05 PM, Jan Sælid wrote:


...



What I want to do is to just change the icon according to the state of
onstate property. Should I use a visited icon or a hilited icon? No  
matter
what I turn off or on I seem to get some additional behaviour. Like  
a border
or the traversal  border. I’m sorry that I have to bother you with  
this but
my early days of lessons is just hidden under layers of other  
priorities.






If all the buttons do is signal a state change that will be acted on  
later, I would put the following script in the group:


   on mouseup
 set the hilite of the target to not (the hilite of the target)
   end mouseup



I would set the hiliteIcon property to get my custom icon. I would  
set the autohilite of the buttons to false, and just to make sure I  
would set the hiliteborder and hilitefill of the buttons to false, too.


If I didn't want a focus border (and I never do), I would set the  
showfocusborder of the buttons AND of the group to false (otherwise,  
in Windows, the dotted line focus border shows up on the buttons  
anyway).


If I want rollover behavior, I would use the new hoverIcon property  
instead of the autoArm and armedIcon property; so I'd set autoArm of  
the buttons to false, and I would set the armBorder and armFill of  
the buttons to false too, for good measure.


I'd set the traversalOn of the group and the buttons to true.

I'd avoid the visitedIcon unless you really have a visited state  
you need to convey (i.e. this button has been clicked already but  
it's not disabled--I guess it's a Unix thing.)



If I need to carry around the state of the buttons (assuming they  
record states), I'd do something like:


   repeat with N = 1 to the number of buttons of grp states
 put the hilite of btn N of grp states into \
tStateArray[the short name of btn N of grp states]
   end repeat

...and then later:

   if tStateArray[meaningfulButtonName] then 



If it's against your religion to conflate a gui state with a program  
state, it's still easier and clearer when you avoid elaborate if  
statements, just to transfer Boolean values; that is, use:


   set the hilite of me to the onstate of me

rather than:

   if the onState of me is true then set the hilite of me to true


HTH,

t


--
Tereza Snyder

   Califex Software, Inc.
   www.califexsoftware.com

--
Tereza Snyder

   Califex Software, Inc.
   www.califexsoftware.com

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Button Basics?

2003-08-19 Thread [EMAIL PROTECTED]
I can't seem to select individual items of a pop-up menu button to enter
their scripts in 
the script editor.  I tried

select menuItem X of button Button Y

in the message box, but when I open the script editor, it's just for the
whole button, not 
the individual items in the button.  What am I missing?


mail2web - Check your email from the web at
http://mail2web.com/ .


___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Button Basics?

2003-08-19 Thread Jan Schenkel
--- [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 I can't seem to select individual items of a pop-up
 menu button to enter
 their scripts in 
 the script editor.  I tried
 
 select menuItem X of button Button Y
 
 in the message box, but when I open the script
 editor, it's just for the
 whole button, not 
 the individual items in the button.  What am I
 missing?
 

Hiya,

You cannot set individual scripts for each item ;
you'll have to script the menu as a whole, and handle
the 'menuPick' message.

Suppose you have a menu with items :
  Alpha
  Beta
  Gamma
  Delta

Example script for that menu button :

on menuPick pWhichItem
  switch pWhichItem
  case Alpha
-- the user chose the item labeled Alpha
-- do what needs done here, before 'break'
break
  case Beta
-- the user chose the item labeled Beta
-- do what needs done here, before 'break'
break
  case Gamma
-- the user chose the item labeled Gamma
-- do what needs done here, before 'break'
break
  case Delta
-- the user chose the item labeled Delta
-- do what needs done here, before 'break'
break
  end switch
end menuPick



An alternative way of scripting the individual items
is the following :

- make individual handlers for what each item needs to
do, in the card script

- put the names of these handlers as a
return-delimited list into a custom property named
uMenuMessages in the menu button

- set the script of the menu button to 

on menuPick
  put the menuHistory of me into tPickedLine
  put line tPickedLine of the uMenuMessages \
  of me into tMenuMessage
  send tMenuMessage to this card
end menuPick



For more information than you may ever want to know
regarding menus, fire up the Revolution Documentation,
go to the section 'Development Guide' and click on the
item 'Menus' in the left-hand list.

Hope this helped,

Jan Schenkel.

=
As we grow older, we grow both wiser and more foolish at the same time.  (La 
Rochefoucauld)

__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Button Basics? -thanks Jan!

2003-08-19 Thread [EMAIL PROTECTED]
Thanks a million to Jan Schenkel!

Problem solved!  I had looked at every single thing in the Menus chapter
of the 
Documentation by Catagory and while I had seen references to MenuPick I 
couldn't make heads or tails out of implementing it.  Sometimes we non
code writers 
know literally nothing and need tips, like the one you gave me, in real
plain English! I 
am following the documentation and beginners discussions closely and have
signed 
up for the Dan Shafer book and I hope to get better at this. Thanks again
and also 
thanks to those of you who answered a couple of other beginners questions
for me in 
the past few weeks!


Lars 


mail2web - Check your email from the web at
http://mail2web.com/ .


___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution