The non-working button problem went away for a while after I realized
that I had some scripts open and edited but not
updated/writen/applied/saved. After I fixed that, things were better.
For a while.
Then the problem appeared again. I Applied/Saved every script I could
find. Some of them did not "take": after I saved them, the Apply
buttons would go back to black again, spontaneously, as if I had never
done the Saves.
Eventually I just killed every script editor. Then it REALLY hit the
fan. There were LOTS of "do you want to save changes or not" messages,
over and over again, as if there were lots of hidden instances of
editors and lots of hidden instances of unsaved script text. I got out
of Rev and came back in. Some of the bottons still don't work.
Rev seems to be pretty buggy to me. Painfully so for a commercial product.
Jon
J. Landman Gay wrote:
On 6/2/05 12:57 PM, Jon wrote:
I created a project with a Player and a Button. The button asks the
user to select an audio file and then assigns the file name to the
Player.
The button worked once, but no longer. Nothing I do gets control
back to the script associated with the button. I even made a new
button and copied the script text to the new button's script. I even
quit out of Rev and came back in. Breakpoints don't help: I never
reach them.
Any thoughts as to what I might have done to accidentally disable a
mouseDown event in a script?
Could be a lot of things. Can you post your example stack somewhere
for us to look at? (The list doesn't allow attachments, you'll need to
post it somewhere else. You could use your free Rev user space.) Or
post the script of your button?
_______________________________________________
use-revolution mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/use-revolution
