I take a crack at this. I think your problems in NS are not so much the
DynAPI and its event structure as much as NS's weakness to handling an
"event overload" caused by your "decathalon like mouse behavior" (you should
be a game tester, the programmers would hate you).
Anyway it's probably causing a recursion error do to an event overloading
and then NS just ignores them. Solution might include a two step process
related to method firing.
1) Create a method (if-then-else or switch) that starts the film widget and
iterates through (x) motions of it before recalling it new or even loading a
"new" image film into it. Think expanded widget power while hopefully
fooling NS into behaving.
2) Have (1) call "filmwidget".
3) repeat.
Hopefully this repeater behavior will restart the film widget frsh should
some "crazy user" manage to hang it. It's possible you could also build a
recursive call that throws an error forcing a widget restart of the "left to
right slide" fails to complete (i.e. I've been HUNG).
Anyway goodluck.
Cheers,
Ray
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-help
