On 6/2/05 2:45 PM, Jon wrote:
> The stack is at www.jonbondy.com/jlblooper.rev. At the moment there are
> four buttons: open, open2, play, and stop. I think Stop works. The
> others do not. I'm developing on a Win XP system, so telling me that it
> works fine on a Mac or under Linux will be interesting but perhaps not
> helpful.
I took a look. I don't see any mouseDown handlers, only mouseUp (which
is what is generally used in buttons, so you are correct to do that.)
Most of your mouseUp handlers have breakpoints set at the first line of
code, so that is why they are stopping, probably. Use the buttons at the
bottom of the script to either abort or continue running the scripts. Or
remove the breakpoints.
Until you get used to it, it is probably a good idea to apply the script
before opening very many others. Knowing that a script is applied and
functional can help track down problems. If a script isn't
applied/saved, the old version will run instead of the one you have just
edited, and your breakpoints won't be pointing to the lines you think
they point to. That may also be why you didn't think there were
breakpoints set.
A couple of other things I noticed:
set the Value of the scrolLBar "ProgressBar" to the currentTime of
player "Player"
This won't work; "value" is a function which evaluates its parameters
and returns the result. For example, "value(22+6)" will return 28. What
you want here is:
set the thumbPosition of scrollbar "progressbar" to the currenttime
of player "player"
Same for the line in the stack script: set the currentValue of the
scrolLBar "ProgressBar" to ct
should be "thumbPosition" (or for short, "thumbpos".)
Another:
Play player "Player"
The "play" command is used for pre-recorded sound files, like .wav files
and such, and doesn't require or use a player object. The "play" command
lets you directly play many types of sound files, either from files on
disk or imported into the stack, without using any containing object at
all. If you want to control a player object (which is required for mp3
files,) you need this command instead:
start player "player"
The "set the tracks" line in one of your buttons is superfluous. This
property is read-only.
You did a good job setting object properties throughout. You learn fast.
Nice start, and pretty good for only being at this for a couple of days.
The initial learning curve is the hardest part. There is a certain
critical mass of info you have to have before it all falls into place,
and that is the most frustrating time. After that, it suddenly starts to
make sense. There is a certain "eureka" moment, after which everything
gets much easier.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/use-revolution
