card rect problem
pmbrig at comcast.net
Fri Oct 27 06:01:34 CDT 2006
Thanks for the suggestions and the offer, Jim. I worked around it by
keeping the card/stack size constant and just resizing the field.
This results in a window for the user to type in that runs off the
bottom of the screen, which is not really esthetic, got the job done
temporarily. I've just finished doing sort of what you suggested,
making a new input substack and using the old one just for the
printing, which avoids resizing the stack window. I'll test it out
today to make sure that solved the problem.
The original question still stands, however -- anyone know how in the
world a card rect could get to be different from the stack rect? I
have not used the geometry manager at all with this substack, so that
seems to be a dead end.... I'm curious, because it shows me there is
something deep I don't get about card vs stack vs window geometry.
Peter M. Brigham, MD
pmbrig at comcast.net
If the universe is expanding, how come I can
never find a parking place?
On Wed, 25 Oct 2006 22:26:27 -0700 Jim Ault <JimAultWins at hidden> wrote:
Re: card rect problem
On 10/25/06 9:12 PM, "Peter Brigham" <pmbrig at hiddenwrote:
I have a problem that's driving me crazy. I'm working on OSX 10.4 on
an iBook G4 with Dreamcard 2.6.1, and I run this particular stack
system under the IDE exclusively. It's a stack for printing clinical
notes, but it has lots of bells & whistles. I have a substack for
Does it have to do with stuff I don't understand about setting the
rect of a stack vs the rect of a window? I sure don't seem to get
something important about the window size vs the card size. What
could be making the card rect be different from the window rect? And
why would this be intermittent? I'm getting pretty frantic, since as
it stands I can't even print my clinical notes properly now and it's
seriously interfering with me managing my practice....
I feel your frustration.
My quick answer would be to do:
Build a subStack that is the print page size, include one or more fields
sized and formatted correctly, copy the original text to the correct
hide the others, then print without having to resize any fields or
stacks (except the header reveal).
It could be that at some point you used the Rev geometry manager for
objects and it remembers some ghost info.
If you need a better answer from me, you should consider sending me a
stack(s) without private information and I will try it on my Mac. My
printing/formatting experience is limited, but it sounds like you need
something very quickly. I can carve out a bit of time to do this.
I have been xTalking since HCard 1.0
More information about the use-livecode