Richard Gaskin writes:
[EMAIL PROTECTED] wrote:
Richard Gaskin writes:
[snip]
Is the printPapersize read-only? If no, have I missed somewhere in both the
MC and Rev docs where it's described as such?
--
Richard Gaskin
==
Probably missed something...
Rev1.1.1
Transcript
I have a stack that keeps quitting with a Type 2 error. I believe it
is a conflict between this stack and Metacard, as other stacks do not
seem to produce this error, but all efforts to track down the problem
have offered no resolution.
So far my best guess is that it lies somewhere in a
I forgot to add that this error only occurs when the stack is a
stack. When I turn it into a standalone, the error seems to go away.
Hence the conclusion that there is a conflict between a script of
mine and a script of Metacard, where the Metacard script does not
exist in the standalone.
Here's a (very) small editing tip some folks might find useful. You can
place this script at the top of the mouseUp handler of any object for which
you edit the script a great deal:
if the optionKey is down then
edit script of me
exit to metacard
end if
I've found it fairly speedy to
Recently, I wrote:
Here's a (very) small editing tip some folks might find useful. You can
place this script at the top of the mouseUp handler of any object for which
you edit the script a great deal:
if the optionKey is down then
edit script of me
exit to metacard
end if
Then
On Friday, May 30, 2003, at 08:19 AM, Shari wrote:
I forgot to add that this error only occurs when the stack is a stack.
When I turn it into a standalone, the error seems to go away. Hence
the conclusion that there is a conflict between a script of mine and a
script of Metacard, where the
On Fri, 2003-05-30 at 19:29, Mark Talluto wrote:
On Friday, May 30, 2003, at 08:19 AM, Shari wrote:
I forgot to add that this error only occurs when the stack is a stack.
When I turn it into a standalone, the error seems to go away. Hence
the conclusion that there is a conflict between
[EMAIL PROTECTED] wrote:
Is the printPapersize read-only? If no, have I missed somewhere in both
the
MC and Rev docs where it's described as such?
--
Richard Gaskin
==
Probably missed something...
Rev1.1.1
Transcript dictionary entry printPaperSize property:
The
Have you tried:
1. A fresh install of MC
2. Running with extensions turned off
3. Testing it in another OS and/or another computer
4. Running Macbus and getting a stdlog file
Best regards,
Mark Talluto
Metacard itself does not run on my computer with extensions off. I
am about to compile it
It's probably a way to
get the sames infos under Jaguar but i did'nt test this for yet.
Bests, Pierre
So far the only thing I've done with the console window in Jaguar is
to meet Eliza, the psycho-analyst. My fella horned in on the
conversation, and he taught Eliza words she never heard of
on 05.30.03 8:07 PM, Shari wrote:
Does anyone know how to pull errors out of the console/terminal
window in Jaguar (whatever the divil that DOS like thang is called...)
Open the console application and check Eenable crash reporting and
Automatically display crash logs in the preferences.
Halo,
if I move fast the scrollbar upwards in the fld show up a lot of lines -
horrible to look at. They disapear, when I click in the fld.
That effect does not appear, when moving the scroll down. Also not, if I
click into the scrollbar to get the scroll up.
Any hints, what btns I could click
12 matches
Mail list logo
