on 2/10/02 12:11 AM, Mark Mitchell at [EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] writes:
> I don't have buttons, I have graphics. Like a square or circle or polygon.
> Any ideas?
>
> I do this sort of thing all the time. Every selection just DEselects all
> objects in the
> group prior to se
I've been following the thread about how to handle graphical hiliting for
an unGodly number of objects, and let me add my voice to the chorus of those
who are wondering what the heck kind of purpose *requires* messing around
with a *five-digit* number of whatever-they-ares.
However, presu
on 2/10/02 4:42 PM, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote:
> I think it should be relatively easy to implement the underlying concept
> in Rev/MetaCard, yes?
--
Yeah, pretty much. This is very cool. There are some things that HC handles
better, but on the other hand, in Rev/MC you
on 2/10/02 10:43 PM, Mark Mitchell at [EMAIL PROTECTED] wrote:
> Or, as someone else suggested, which might be a little more intuitive than the
> script above,
> simply set a customProperty of your group to the currently selected, then
> deselect that using
> a group script. Frankly, I'm not sur
On Mon, 11 Feb 2002 Rob Cozens <[EMAIL PROTECTED]> wrote:
>
> >I did, Rob, in my post of 11th. Without the detail, it showed HC about
> >5% faster with screen unlocked and 6x (!) faster with screen locked
>
> Sorry I didn't look close enough to notice, David.
>
> I must admit I am surprised, as
On Tuesday, February 12, 2002, at 10:53 , Rob Cozens wrote:
snip
> I must admit I am surprised, as I've followed Scott Rainey's work to
> accelerate the MetaCard engine since early discussions on the HyperCard
> List.
>
> Rob Cozens
> CCW, Serendipity Software Company
>
I guess HyperCard accelerat
On Tuesday, February 12, 2002, at 11:36 , Scott Raney wrote:
> snip
> HyperCard *is* faster at field get/set and reformatting. It's just the
> price you pay for breaking the 32K and color barriers. Fortunately in
> most cases MetaCard's on average 5x better performance on everything
> else mor
>HyperCard *is* faster at field get/set and reformatting. It's just the
>price you pay for breaking the 32K and color barriers.
I can certainly understand that, Scott, and it brings up another question:
With color built in, is there any porential performance advantage in
keeping a performance-
On Tue, 12 Feb 2002 Rob Cozens <[EMAIL PROTECTED]> wrote:
> >HyperCard *is* faster at field get/set and reformatting. It's just the
> >price you pay for breaking the 32K and color barriers.
>
> I can certainly understand that, Scott, and it brings up another question:
>
> With color built in,
