windowShape revisited

[richmond62]

So, I have a stack with a graphic line on it:
-

-
and the button contains this code:

Code: Select all

on mouseUp
   import snapshot from grc "myLine"
   if exists(img "shadow") then
      delete img "shadow"
   end if
   set the name of the last control to "shadow"
   set the layer of img "shadow" to 1
   set the loc of img "shadow" to the loc of grc "myLine"
   set the windowShape of this stack to the ID of img "shadow"
end mouseUp

which is fairly pedestrian and, apparently, straightforward,

BUT the end result is this:
-

-
which it should not be; the alignment being, as we say in Scotland, "agley" or "aff".

[richmond62]

Code: Select all

on mouseUp
   import snapshot from grc "myLine"
   if exists(img "shadow") then
      delete img "shadow"
   end if
   set the name of the last control to "shadow"
   set the layer of img "shadow" to 1
   set the loc of img "shadow" to the loc of grc "myLine"
   --- additions
   set the top of grc "myLine" to the top of card "c1"
   set the left of grc "myLine" to the left of card "c1"
   ----
   set the windowShape of this stack to the ID of img "shadow"
end mouseUp

Well, here we go again, I end up answering my own question as really cannot wait . . .
-

-
And that is NOT documented.

[FourthWorld]

"that"?

[richmond62]

THAT the topleft of the image that is used as the reference for the windowShape
must be 0,0; the topleft of the card of the stack.

[richmond62]

ACTUALLY 'THAT' is what prevents one from developing some sort of 'squiggle board' in LiveCode
where an end-user can use the brushTool to draw on top of their desktop: because any masking would
shift their squiggles top-and-left in a disconcerting way UNLESS the whole thing was contained
inwith a FRAME.

[richmond62]

-
Getting 'there' [wherever 'there' is ].

[richmond62]

-
HOWEVER . . . with this script in the octagon:

Code: Select all

on mouseEnter
   choose browse tool
end mouseEnter

on mouseLeave
   choose brush tool
end mouseLeave

the mouseLeave code works,

but

the mouseEnter does NOT.

What should happen is something like this:
-

[richmond62]

Presumably the reason for this is because choose brush tool sets up an image at a higher
layer than the object containing the mouseEnter code.

There seems no obvious way to circumvent this.