In deference to Shari, I think she's talking about protecting the *data* in
the stack, not the scripts. Even a password protected and cantModify-ed
stack can still be opened in MetaCard and the cards freely viewed.
Shari, if this is your concern, my suggestion would be to keep card 1 of
your data
Doesn't work either.
Under most Unices you would use quotes to close the filename:
cd /Volumes/"Mac OS X"
This works if I run it through shell(), but that's not what I'm
trying to do. I want to set the directory internally to MC,
driving me a little nuts at the moment.
On Friday, June 28, 2
My posts sometimes appear to get eaten along the way...
Begin forwarded message:
> From: Simon Lord <[EMAIL PROTECTED]>
> Date: Thu Jun 27, 2002 11:36:41 PM America/Montreal
> To: [EMAIL PROTECTED]
> Subject: Current drive name
>
> This is a Mac OSX related question.
>
> When I get the full pat
<< I wonder if this is a OSX problem, but the following does not
work at all:
set the directory to "/Volumes/Mac OS X"
I cannot set the directory to any path that has spaces in the filename. >>
What happens if you escape the spaces:
set the directory to "/Volumnes/Mac\ OS\ X"
I think that's
I wonder if this is a OSX problem, but the following does not
work at all:
set the directory to "/Volumes/Mac OS X"
I cannot set the directory to any path that has spaces in the filename.
On Wednesday, June 26, 2002, at 06:54 AM, Klaus Major wrote:
> set the directory to "/Mac OS X"
Sincerely
This is a Mac OSX related question.
When I get the full path to my stack it returns something like this:
stack "/Applications/MetaCard/directory-navigation.mc"
My question is, how can I tell which *drive* the stack is on? I
have upwards of 5 drives (3 internal, 2 external). My stack has
it'
On 6/27/02 7:02 PM, Shari wrote:
>
> But if you are creating a standalone to distribute, a password is a bad
> thing. The objective is to create a program, to distribute, but have
> whatever data you want "hidden" to remain that way even if someone tries
> to get into it. It is easier to "br
Recently, "Shari" wrote:
>> Such protections are afforded all password-protected stacks, standalone or
>> not.
>
> But if you are creating a standalone to distribute, a password is a
> bad thing. The objective is to create a program, to distribute, but
> have whatever data you want "hidden" to
--On Thursday, June 27, 2002 20:02:34 -0400 Shari <[EMAIL PROTECTED]>
wrote:
>> Such protections are afforded all password-protected stacks, standalone
>> or not.
>
> But if you are creating a standalone to distribute, a password is a bad
> thing. The objective is to create a program, to dist
>Such protections are afforded all password-protected stacks, standalone or
>not.
But if you are creating a standalone to distribute, a password is a
bad thing. The objective is to create a program, to distribute, but
have whatever data you want "hidden" to remain that way even if
someone tri
In a message dated 6/27/2002 7:39:12 PM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
<< He seems to have no problem running it on the command line but as cgi,
which means that Apache must look for something like /cgi-bin/script.cgi.
If I understand you correctly the script should have in
--On Thursday, June 27, 2002 17:08:45 -0600 Scott Raney
<[EMAIL PROTECTED]> wrote:
> On Fri, 21 Jun 2002 [EMAIL PROTECTED] wrote:
>
>> I can't seem to figure out how to run a cgi script with 2.4.3.
>> The following works with MC/Darwin as a cgi script with apache:
>>
>> # !mc
>> # file: test.m
On Fri, 21 Jun 2002 [EMAIL PROTECTED] wrote:
> I can't seem to figure out how to run a cgi script with 2.4.3.
> The following works with MC/Darwin as a cgi script with apache:
>
> #!mc
> # file: test.mt
> on startup
> ..
> end startup
>
> After installing the MetacardCarbon/Mach-O bundle in the
Shari wrote:
>> Recently, Simon Lord wrote:
>>
>>> Is it possible to have a standalone make changes to itself and
>>> actually save those changes?
>>
>> Nope. You can only edit/save (non-standalone) stacks. You can get close to
>> what you ask by keeping the bulk of your scripts in a stack an
>Something hosed my menubar, and I can't figure out how to fix it.
>
>I have a group named "menugroup", with a button "menubutton", and
>"File" and a few others with "Help" last.
>
>I have the stack set to show "menugroup" on Mac.
>
>But it doesn't recogize "menugroup" and there's no Mac menubar.
At 11:18 am -0700 25/6/02, Richard Gaskin wrote:
>Hmmm... still stumped on how to proceed, I'm afraid.
I think I misunderstood the original problem.
>
>Here's the relevant snippet from my script:
>
>put "ftp://"&; tUser &":"& tPword &"@"& tHost &\
> "/"& tDir &"/" into tBaseDestUrl
>
>> You can only edit/save (non-standalone) stacks. You can get close to
>> what you ask by keeping the bulk of your scripts in a stack and using a
>> small standalone engine to run the stack -- changes are save by the engine
>> to the stack.
> Doesn't that defeat the purpose of using a standalon
--On Thursday, June 27, 2002 11:57:24 -0400 Shari <[EMAIL PROTECTED]>
wrote:
>> Actually, you can protect a stack as well as a standalone. Set the
>> cantModify to true, give it a password and save it. The only thing
>> someone with MC will be able to do is open your stack and view the cards
>
>Actually, you can protect a stack as well as a standalone. Set the
>cantModify to true, give it a password and save it. The only thing someone
>with MC will be able to do is open your stack and view the cards - they
>won't be able to view or change scripts, and even if they move objects
>around,
Shari,
Actually, you can protect a stack as well as a standalone. Set the
cantModify to true, give it a password and save it. The only thing someone
with MC will be able to do is open your stack and view the cards - they
won't be able to view or change scripts, and even if they move objects
aroun
>Recently, Simon Lord wrote:
>
>> Is it possible to have a standalone make changes to itself and
>> actually save those changes?
>
>Nope. You can only edit/save (non-standalone) stacks. You can get close to
>what you ask by keeping the bulk of your scripts in a stack and using a
>small standal
What problem?
82.845 rounded to 2 decimal places should round to 82.84
Whereas, 82.835 would also round to 82.84
The rule is whenever you have a perfect half (i.e. the last significant
digit is a 5) and you are rounding to the next digit, then you should round
to the nearest even number. That w
22 matches
Mail list logo
