I noticed in the latest DL of MetaCard, the alwaysBuffer of most IDE
stacks is not set. While this was not necessary in previous versions of
the engine, it is now used to disable the 'flashing' effect around
windowsXP look and feel.
I recommend setting the alwaysBuffer of all IDE stacks to true
[EMAIL PROTECTED] wrote:
>> So I'm proposing that I add this very simple function the
>> the MC IDE backscript:
>>
>> function revAppVersion
>> return "0"
>> end revAppVersion
>>
>> This function follows the convention established by the qtVersion
>> function, returning a version nu
Chipp Walters wrote:
I noticed in the latest DL of MetaCard, the alwaysBuffer of most IDE
stacks is not set. While this was not necessary in previous versions of
the engine, it is now used to disable the 'flashing' effect around
windowsXP look and feel.
I recommend setting the alwaysBuffer of a
Hi Richard,
...
So I'm proposing that I add this very simple function the the MC IDE
backscript:
function revAppVersion
return "0"
end revAppVersion
This function follows the convention established by the qtVersion
function, returning a version number if present (this function is
available i
alwaysBuffer not set...
Richard Gaskin ambassador at fourthworld.com
Tue Jul 20 12:27:24 EDT 2004
* Previous message: alwaysBuffer not set...
* Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chipp Walters wrote:
> I noticed in the latest DL of MetaCard, the alwaysBuffer of m
Wouter wrote:
> I noticed in the latest DL of MetaCard, the alwaysBuffer of most IDE
> stacks is not set. While this was not necessary in previous versions of
> the engine, it is now used to disable the 'flashing' effect around
> windowsXP look and feel.
>
> I recommend setting the alwaysBuffer of
alwaysBuffer not set...
Richard Gaskin ambassador at fourthworld.com
Tue Jul 20 14:46:17 EDT 2004
-- snip
Re-reading Chipp's post more carefully, he's referring only to IDE
stacks, and yes, the IDE stacks should have their alwaysBuffer set to
true.
Can anyone think of a reason not to? Unless some
Wouter wrote:
Re-reading Chipp's post more carefully, he's referring only to IDE
stacks, and yes, the IDE stacks should have their alwaysBuffer set to
true.
Can anyone think of a reason not to? Unless someone tells me not to I'm
inclined to do it for the next release.
As for doing that for all new
alwaysBuffer not set...
Richard Gaskin ambassador at fourthworld.com
Tue Jul 20 16:13:47 EDT 2004
* Previous message: alwaysBuffer not set...
* Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wouter wrote:
--big snip
> If this is at engine level then the engine itself is maki
--- Wouter
> I look at MC and RR as stacks interacting with
> an engine ... but the impression is growing that
> what is called the engine, is something composed
> of stacks and the engine. Where are the borders
> between the IDE, stacks and the engine?
Very *VERY* good point, Wouter.
Where is
Hello Wouter and y'all,
> Only wondering why slowly all those little
> differences are creeping in. Undocumented
> little changes, to be discovered by
> (sometimes enervated :-) users.
This may be stretching this out of context but I would
like to chipin that more & more software, particularly
w
Alain Farmer wrote:
Hello Wouter and y'all,
Only wondering why slowly all those little
differences are creeping in. Undocumented
little changes, to be discovered by
(sometimes enervated :-) users.
This may be stretching this out of context but I would
like to chipin that more & more software, pa
Alain Farmer wrote:
Wouter wrote:
I look at MC and RR as stacks interacting with
an engine ... but the impression is growing that
what is called the engine, is something composed
of stacks and the engine. Where are the borders
between the IDE, stacks and the engine?
Very *VERY* good point, Wouter.
Hi Richard et al...
I agree with Richard, in fact, his often well-thought expression of
MetaCard's strict compliance to the vanilla is the primary reason why
I'm 'attempting' to switch to MC (I'm sure a first, going back to MC
from one who has started with RR:-)
I believe the alwaysBuffer shoul
for what it's worth,
I'm doing the following:
if there is a stack "revMenuBar" then
--IN REV
else
--IN MC
end if
also, I notice libURL doesn't start automatically, but my
altPluginsToolbar (and MagicCarpet and other plugins) need it. So, in MC
I use in my altPlugin toolbar initMe routine the
Chipp Walters wrote:
for what it's worth,
I'm doing the following:
if there is a stack "revMenuBar" then
--IN REV
else
--IN MC
end if
LOL - I'd been doing the opposite, checking for "MetaCard Menu Bar". :)
also, I notice libURL doesn't start automatically, but my
altPluginsToolbar (and MagicCa
On 7/20/04 8:36 PM, Richard Gaskin wrote:
I had made a shell that lets you import the content of the Rev
Transcript Dictionary -- I should post it to the MC Group at Yahoo for
review.
Except the new Rev docs are individual XML files. Will you rewrite your
importer? ;)
--
Jacqueline Landman Gay
On 7/20/04 10:06 PM, Chipp Walters wrote:
also, I notice libURL doesn't start automatically, but my
altPluginsToolbar (and MagicCarpet and other plugins) need it. So, in MC
I use in my altPlugin toolbar initMe routine the following:
try
get libURLVersion()
catch tErr
start using stack libURL
18 matches
Mail list logo