Nudging shapes

[Robert Westmoreland]

I repeated your experiment, and got the same results that you describe.
Thanks for looking into this.

-- Robert

> From: David Kasprzyk <support at omnigroup.com>
> Date: Fri, 28 Dec 2001 13:59:45 -0800
> To: Howard Kaufman <hkaufman at mindspring.com>, Robert Westmoreland
> <khr at earthlink.net>, omnigraffle-users at omnigroup.com
> Subject: Re: Nudging shapes
> 
> Howard and Robert:
> 
> All I have to say about this is that it is the weirdest bug that I have
> encountered in OmniGraffle.  Here is what I have been able to uncover
> about this problem.
> 
> When I first opened up Howard's file that he sent me and started a new
> text box, the problem did not appear.  So I selected one of the text
> elements in Howard's text example and behold, I encountered the exact
> problem that both of you described.  Well I found this very confusing,
> so I tried experimenting with several different ideas without success.
> 
> Finally, I opened up the fonts window and here's where I uncovered the
> problem.  It seems that this issue is related to the font and size of
> the text.  The font of Howard's text boxes was Geneva, while my default
> font is Gill Sans.  So when I was using Geneva I experienced the
> problem, but not with Gill Sans.
> 
> If you want to see what I'm talking about here's a little experiment to
> try out:
> 
> Create four text box's each with a different font.  For experiment use
> the following fonts all at size 14; Gill Sans, Georgia, Geneva, and
> Futura.  With Georgia and Gill Sans, the text should type normally, even
> with new lines.  With Geneva, after you enter a newline you can no
> longer see what you are typing.  With Futura you can't even see the
> initial text that you start to type.
> 
> Now use the same fonts but all at size 12.  Now with Georgia, Gill Sans,
> and Geneva the text should type normally, even with new lines.  And with
> Futura, after you enter a newline you can no longer see what you are
> typing but you can see you initial typing now.
> 
> So what I think we are doing is setting our bounding boxes for the text
> too small when we can't see the text.  If we increase these bounds I
> think the problem will no longer be a factor.
> 
> Let me know if any of you experience anything differently than this.  As
> always, keep sending in your bugs, comments, and questions.
> 
> Sincerely,
> 
> David Kasprzyk
> support at omnigroup.com
> 
> Join the OmniGraffle Users List
> http://www.omnigroup.com/mailman/listinfo/omnigraffle-users
> 
> On Wednesday, December 26, 2001, at 07:07  PM, Howard Kaufman wrote:
> 
>>>> I notice that when typing text in a new text box, you can use
>>>> option-return to get a new line.  The box expands for the new line,
>>>> but
>>>> the  text itself doesn't show up until you finish typing.  So after
>>>> the
>>>> first line, you are typing "blind".
>>> 
>>> Hmm, well I couldn't get this issue to appear on my machines.  Can you
>>> send in a .graffle file that you have this problem in?
>> 
>> I will attach a file, but the problem may also be with my description of
>> the  problem.  Let me try again to explain it.  If I start a text box
>> with
>> the text tool, sometimes I want it to have line breaks where I want
>> them.
>> So far so good.  So I read that you can have a new line with the command
>> Option-return.  When I do this the text box adds a new blank line below
>> the
>> line I was typing.  The problem is if I keep typing, the text I enter is
>> not showing up in the new line. I also lose the insertion cursor.   If I
>> stop and click outside of the text box, then the new characters do
>> appear.
> 
> 
> On Wednesday, December 26, 2001, at 08:49  PM, Robert Westmoreland wrote:
> 
> From: Robert Westmoreland <khr at earthlink.net>
> Date: Wed Dec 26, 2001  08:49:51  PM US/Pacific
> To: David Kasprzyk <support at omnigroup.com>, Howard Kaufman
> <hkaufman at mindspring.com>
> Cc: <omnigraffle-users at omnigroup.com>
> Subject: Re: Nudging shapes
> 
> For the record, I experienced this same bug with the release version of
> OG.
> I did not report it because I was typing Japanese at the time, and
> thought
> it was probably a bug in the OS X Japanese input system. (Also, because
> I am
> lazy.) However, I am not able to repro it now (with the beta (2.0b3) and
> OS
> X 10.1.2).
> 
>