A followup to my message on same thread, posted a few minutes ago, in reply to
Paul.
Further investigation reveals this anomaly: If I make the stack height a little
too big, so the stack crops itself when it opens, and I then click on the
little glowing green button at the upper left of the LC
Hi Paul,
I'm on OS 10.6.8
I'll bet it's the dock. Wait. I'll try it right now...
Oopsie! Same issue with the dock on the left.
For now, this behavior is replicable.
Trial and error: If I set the height to 717, close and reopen, it stays at 717.
Same for 718. If I set it to 719, close and re-o
Tim,
Are you using OS X?
Two things on OS X can cause vertical resizing problems:
1. The dock
If the dock is on the bottom of the screen (even if it is hidden)
stacks can be shortened to accommodate area for the dock. Try it on
the side and see if that makes a difference.
2. Menus
All usually
FYI, on a mac, the the working screenrect gives you the screenrect minus the
height of the mac menubar (22).
Does this work for you?
on preopenstack
set the width of this stack to 612
set the height of this stack to 792
set the top of this stack to 110 -- or whatever
end preopenstack
When
What I did a long time ago to resolve this is I created a background graphic
the size I wanted my window to be. The stack always seems to open at the right
size now.
Bob
On Aug 10, 2011, at 1:29 PM, Timothy Miller wrote:
> My query from earlier this morning is generating a non-flurry of repl
Hi Tim,
If the stack is taller (or wider) than governed by the windowBoundingRect, it
will be automatically chopped off. I do not like it... Been that way for ever.
:-(
Cheers,
Malte
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please
My query from earlier this morning is generating a non-flurry of replies,
likely because no one knows the answer.
I have solved the problem with a simple preOpenStack handler, which works fine.
However, I feel this issue must represent a gap in my knowledge, which I would
like to close.
Furthe
On 23/11/2010 22:55, FlexibleLearning wrote:
We were getting a
'cannot find stack' error which actually meant 'cannot fully load this
stack', as well as no graceful result that memory is running low; just a
suddenly non-responsive stack. I think a bit of work is needed at the upper
end of memory
FlexibleLearning wrote:
> Thank you Jacque... Forgot about that one. Had half-remembered it as a
> compatibility-only function, but we'll give it a try. We were getting a
> 'cannot find stack' error which actually meant 'cannot fully load this
> stack', as well as no graceful result that memory is
FlexibleLearning wrote:
Thank you Jacque... Forgot about that one. Had half-remembered it as a
compatibility-only function, but we'll give it a try. We were getting a
'cannot find stack' error which actually meant 'cannot fully load this
stack', as well as no graceful result that memory is runni
Thank you Jacque... Forgot about that one. Had half-remembered it as a
compatibility-only function, but we'll give it a try. We were getting a
'cannot find stack' error which actually meant 'cannot fully load this
stack', as well as no graceful result that memory is running low; just a
suddenly non
On 11/23/10 3:04 AM, FlexibleLearning wrote:
As data is added to a particular stack, LiveCode runs the risk of running
out of memory. Has anyone figured out how to check this programmatically, or
is it a question for Edinburgh?
I'm not sure you can do it exactly. You could check the size of the
12 matches
Mail list logo
