Re: Problems With Grouped Buttons
>I have a simple stack with seven buttons, each set to arm on >mouseEnter. With seven ungrouped buttons, everything works fine; >however in a second copy of the stack where I have grouped the same >seven buttons the behavior is much different I have done some further testing, and report the following: 1. If the button's 3D property is not checked, a border is drawn around the button on mouseLeave. That border remains until another button in the group receives mouseEnter. 2. If a button's Show Border box is checked, the button will not arm on enter. 3. Without this handler in the group script: on mouseLeave if "button" is not word 1 of the target then exit mouseLeave set the arm of the target to false end mouseLeave An armed button remains armed until another button in the group receives mouseEnter. -- Rob Cozens CCW, Serendipity Software Company http://www.oenolog.com/who.htm "And I, which was two fooles, do so grow three; Who are a little wise, the best fooles bee." from "The Triple Foole" by John Donne (1572-1631) ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Problems With Grouped Buttons
>Set the radioBehavior of the group to false and that should take >care of your problem. Thanks Ken, But I did & it didn't. I went to the App Overview, selected the group & clicked on Properties, then on Group. The "Allow Hiliting Only One Radio Button At A Time" box is dim (perhaps because none of my buttons are radio buttons); so I set radioBehavior via the message box. I'm still getting the same behavior...I'll try to find some time to test this further and report more details. It doesn't seem to make a difference whether the group layer is above or below the individual button layers. As an aside, I noticed I can set a button's style to opaque via the message box, but if I pull down on the button's style popup opaque is not an option. -- Rob Cozens CCW, Serendipity Software Company http://www.oenolog.com/who.htm "And I, which was two fooles, do so grow three; Who are a little wise, the best fooles bee." from "The Triple Foole" by John Donne (1572-1631) ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Problems With Grouped Buttons
Title: Problems With Grouped Buttons Rob, Set the radioBehavior of the group to false and that should take care of your problem. Ken RaySons of Thunder SoftwareEmail: [EMAIL PROTECTED]Web Site: http://www.sonsothunder.com/ - Original Message - From: Rob Cozens To: [EMAIL PROTECTED] Sent: Friday, May 03, 2002 7:21 PM Subject: Problems With Grouped Buttons Hi All, I have a simple stack with seven buttons, each set to arm on mouseEnter. With seven ungrouped buttons, everything works fine; however in a second copy of the stack where I have grouped the same seven buttons the behavior is much different, especially when the mouse passes out of a button into the rectangle of the group. In those cases the buttons seem to act like radio buttons: a button hilited on mouseEnter wont unhilite until another button in the group receives mouseEnter. In addition, the button image changes (a border is drawn around it?) until it is unhilited. What am I missing? Rob CozensCCW, Serendipity Software Companyhttp://www.oenolog.com/who.htm"And I, which was two fooles, do so grow three;Who are a little wise, the best fooles bee."from "The Triple Foole" by John Donne (1572-1631)
