Thomas McGrath III wrote:
Pardon me chiming in here.
When using things like players and speech etc. it is our
responsibility to close them ourselves in our code when and if for any
reason our program is to quit. So I would put a piece of script in a
on closeStack that takes care of the
Perhaps we should have a feature request that always does this
automatically for everyone? All of this kind of stuff is taken care of
automatically in the other IDEs I use...
:)
Jon
Thomas McGrath III wrote:
Pardon me chiming in here.
When using things like players and speech etc. it is
On Jul 28, 2005, at 4:53 AM, Alex Tweedly wrote:
Thomas McGrath III wrote:
Pardon me chiming in here.
When using things like players and speech etc. it is our
responsibility to close them ourselves in our code when and if for
any reason our program is to quit. So I would put a piece of
Alex,
Now that's confusing. ;-)
I always think of Player when I see Player and not Player as in
Dreamcard Player.
I will now have to pay a bit more attention to Player on the list.
Thanks,
Tom
On Jul 28, 2005, at 4:53 AM, Alex Tweedly wrote:
Quite right - except that the context here is
Thomas McGrath III wrote:
When using things like players and speech etc. it is our
responsibility to close them ourselves in our code when and if for
any reason our program is to quit. So I would put a piece of script
in a on closeStack that takes care of the player when closing.
This is
Jac,
I was actually referring to grabbing video in QT (referring to it
being a player type object) as in:
In stack: (this is to clean it up on quit/close of stack)
on closeStack
revCloseVideoGrabber
end closeStack
In Initialize button:
on mouseUp
revInitializeVideoGrabber short name of
Thomas McGrath III wrote:
It is my understanding that not calling revCloseVideoGrabber on
quit/close could cause memory problems.
Oh, I see. Yes, that's right. I was thinking of plain old players that
run QT movies.
But it turns out the original thread was about the Dreamcard Player
Jac,
Yeah I posted 'all' of that mainly for the sake of others that were
reading this thread. I knew you would pick it up right away if I just
said revCloseVideoGrabber but I figured completeness was a good idea.
Player becomes a very general term now, and I don't know how to feel
about
1. The problem I reported about the disappearing cursor does have a
temporary solution, which I got from one of the comments in the
Bugzilla report: include in some stack script the lines
delete stack revCursors
reset cursors
Presto. And that should suggest a fix for the bug,
probably...
but a close window = closerequest = quit should do it
nothing major...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Charles Hartman
Sent: Wednesday, July 27, 2005 20:14
To: How to use Revolution
Subject: Mac-Win revisited
1
Charles Hartman wrote:
2. Is there some way to quit the Dreamcard Player in Windows without
Ctrl-Alt-Delete? Do I have to build an entire menu system just for
that, which I have no use for in the Mac version?
Quit the Player itself, or the stack you are currently playing ?
In either
On Jul 27, 2005, at 3:29 PM, Alex Tweedly wrote:
2. Is there some way to quit the Dreamcard Player in Windows
without Ctrl-Alt-Delete? Do I have to build an entire menu system
just for that, which I have no use for in the Mac version?
Quit the Player itself, or the stack you are
Charles Hartman wrote:
On Jul 27, 2005, at 3:29 PM, Alex Tweedly wrote:
2. Is there some way to quit the Dreamcard Player in Windows
without Ctrl-Alt-Delete? Do I have to build an entire menu system
just for that, which I have no use for in the Mac version?
Quit the Player itself,
On Jul 27, 2005, at 4:50 PM, Alex Tweedly wrote:
Yes it does work, exactly as I and other Windows users would expect
it to work. It closes the app (or window) in whose title bar you
are at the time (or which has focus when you do Alt-F4). That's
what Windows *always* does.
Yes, I
Pardon me chiming in here.
When using things like players and speech etc. it is our responsibility
to close them ourselves in our code when and if for any reason our
program is to quit. So I would put a piece of script in a on closeStack
that takes care of the player when closing.
This is
15 matches
Mail list logo
