Re: Strange button
> I found the problem, and anyone on the list who doesn't already know this > might find it interesting. Originally I had used a button, but then I > switched to an image/control. Embedded within the 350 lines of script were > two little words left over from when I was using a button: . > (This was temporary, while another action was occurring.) I had always > assumed that you couldn't "disable" an image, as there's no checkbox for it > in the Object Inspector. But, it seems, if you "disable" an image by script > (disable me), you will make it transparent to a click. Is this a feature or > a bug? Aaah, never thought of that. Not a bug I would say. Any object can be disabled and when disabled, it should not react to any user input. Cheers, Sarah ___ 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: Strange button
Hi Sarah: I found the problem, and anyone on the list who doesn't already know this might find it interesting. Originally I had used a button, but then I switched to an image/control. Embedded within the 350 lines of script were two little words left over from when I was using a button: . (This was temporary, while another action was occurring.) I had always assumed that you couldn't "disable" an image, as there's no checkbox for it in the Object Inspector. But, it seems, if you "disable" an image by script (disable me), you will make it transparent to a click. Is this a feature or a bug? Anyway, it's working now. Paul Gabel --- On Jul 15, 2009, at 4:17 PM, Sarah Reichelt wrote: I have a button that resides inside of a "background" group (on many cards). The group is script-less. The button has about 10 handlers and 350 lines of script. When I created the button, it worked fine once. But something in its script causes the button, from that point forward, not to trap a click. Instead, a click on it goes to the card. As a workaround I had to write a script at the card level sending a mouseUp back to the button. This works. Now, due to various circumstances, I have to fix this, but I have no idea what in the script could cause such (for me) unprecedented behavior. The script has no errors. If I create a brand new button (in the group) and transfer the script, it does the same thing — works once then becomes transparent to a click. All I am asking is: What KINDS of things should I be looking for? In general, what could make this happen? I would check for a line in the script that is changing the layer of the button or group so that it is being hidden underneath another object. Check the Application Browser to see where your button and it's group before you click and again after you click and see if it changes. HTH, Sarah ___ 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: Strange button
Hi Sarah: Thanks for your suggestions. However, experimenting with the layers doesn't seem to help. When I maneuver the troublesome button (actually it's an image/control) to the front or the back layer of the controls within the group, it doesn't change the situation. No other image/ control within this group has this problem, so it has to be something inside its 350 lines of script. (BTW, The image/control has a blendLevel of 0.) The salient fact is that when I use option-command-click on the image/ control (residing in the group), the script editor shows the card script rather than the image/control script (there is no group script). Any other thoughts on this subject would sure be welcome. Paul Gabel --- On Jul 15, 2009, at 4:17 PM, Sarah Reichelt wrote: I have a button that resides inside of a "background" group (on many cards). The group is script-less. The button has about 10 handlers and 350 lines of script. When I created the button, it worked fine once. But something in its script causes the button, from that point forward, not to trap a click. Instead, a click on it goes to the card. As a workaround I had to write a script at the card level sending a mouseUp back to the button. This works. Now, due to various circumstances, I have to fix this, but I have no idea what in the script could cause such (for me) unprecedented behavior. The script has no errors. If I create a brand new button (in the group) and transfer the script, it does the same thing — works once then becomes transparent to a click. All I am asking is: What KINDS of things should I be looking for? In general, what could make this happen? I would check for a line in the script that is changing the layer of the button or group so that it is being hidden underneath another object. Check the Application Browser to see where your button and it's group before you click and again after you click and see if it changes. HTH, Sarah ___ 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: Strange button
> I have a button that resides inside of a "background" group (on many cards). > The group is script-less. The button has about 10 handlers and 350 lines of > script. When I created the button, it worked fine once. But something in its > script causes the button, from that point forward, not to trap a click. > Instead, a click on it goes to the card. As a workaround I had to write a > script at the card level sending a mouseUp back to the button. This works. > Now, due to various circumstances, I have to fix this, but I have no idea > what in the script could cause such (for me) unprecedented behavior. The > script has no errors. > > If I create a brand new button (in the group) and transfer the script, it > does the same thing — works once then becomes transparent to a click. > > All I am asking is: What KINDS of things should I be looking for? In > general, what could make this happen? I would check for a line in the script that is changing the layer of the button or group so that it is being hidden underneath another object. Check the Application Browser to see where your button and it's group before you click and again after you click and see if it changes. HTH, Sarah ___ 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
Strange button
Hello to everyone: I have a button that resides inside of a "background" group (on many cards). The group is script-less. The button has about 10 handlers and 350 lines of script. When I created the button, it worked fine once. But something in its script causes the button, from that point forward, not to trap a click. Instead, a click on it goes to the card. As a workaround I had to write a script at the card level sending a mouseUp back to the button. This works. Now, due to various circumstances, I have to fix this, but I have no idea what in the script could cause such (for me) unprecedented behavior. The script has no errors. If I create a brand new button (in the group) and transfer the script, it does the same thing — works once then becomes transparent to a click. All I am asking is: What KINDS of things should I be looking for? In general, what could make this happen? Thank you, Paul Gabel___ 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
