Re: Cursed by insertions

2011-02-28 Thread Peter Haworth
Got it, thanks. Pete Haworth http://www.mollysrevenge.com http://www.sonicbids.com/MollysRevenge http://www.myspace.com/mollysrevengeband On Feb 28, 2011, at 9:06 AM, Devin Asay wrote: > > On Feb 28, 2011, at 10:02 AM, Peter Haworth wrote: > >> Just voted. Also added a comment a

Re: Cursed by insertions

2011-02-28 Thread Devin Asay
On Feb 28, 2011, at 10:02 AM, Peter Haworth wrote: > Just voted. Also added a comment about what happens when you switch back > using command-tab (on a Mac). > > This is the first time I've voted for a bugfix/enhancement. I notice I am > allowed 100 votes. Is that a lifetime limit, per bugf

Re: Cursed by insertions

2011-02-28 Thread Peter Haworth
Just voted. Also added a comment about what happens when you switch back using command-tab (on a Mac). This is the first time I've voted for a bugfix/enhancement. I notice I am allowed 100 votes. Is that a lifetime limit, per bugfix/enhancement or some other scheme? Pete Haworth http

Re: Cursed by insertions

2011-02-28 Thread Devin Asay
On Feb 27, 2011, at 2:23 PM, Peter Haworth wrote: > OK, having re-read your original post, I understand what you want, we're > talking about two different problems I think. > > I want the insertion point to stay where it was in LC when I switch to > another app then back to LC. When I switc

Re: Cursed by insertions

2011-02-27 Thread Peter Haworth
Thanks, that sounds like it should work. I have front scripts for suspendstack and resumestack already so this should be pretty easy. Pete Haworth On Feb 27, 2011, at 1:30 PM, J. Landman Gay wrote: > On 2/27/11 2:12 PM, Peter Haworth wrote: >> I think Richmond is referring to the insertion po

Re: Cursed by insertions

2011-02-27 Thread J. Landman Gay
On 2/27/11 2:12 PM, Peter Haworth wrote: I think Richmond is referring to the insertion point, not the cursor. He says no, but you've brought up a related issue. I have noticed this before - if you place the insertion point somewhere in an LC control, switch to another application, then switc

Re: Cursed by insertions

2011-02-27 Thread Peter Haworth
OK, having re-read your original post, I understand what you want, we're talking about two different problems I think. I want the insertion point to stay where it was in LC when I switch to another app then back to LC. When I switch around between any other apps on my Mac, that always happen

Re: Cursed by insertions

2011-02-27 Thread Richmond
On 02/27/2011 10:12 PM, Peter Haworth wrote: I think Richmond is referring to the insertion point, not the cursor. No; I'm not; but I think my Beta tester is getting a bit confused in this way. I have noticed this before - if you place the insertion point somewhere in an LC control, switch

Re: Cursed by insertions

2011-02-27 Thread Peter Haworth
I think Richmond is referring to the insertion point, not the cursor. I have noticed this before - if you place the insertion point somewhere in an LC control, switch to another application, then switch back to LC, the insertion point is gone. This is on a Mac. Other applications on the Mac d

Re: Cursed by insertions

2011-02-27 Thread Richmond
On 02/27/2011 09:00 PM, J. Landman Gay wrote: On 2/27/11 3:30 AM, Richmond wrote: Having made a jazzy cursor for my text field I am wondering if there is possibly a way where, after an insertion point has been decided on, the cursor can remain with the insertion point unless the user moves it.

Re: Cursed by insertions

2011-02-27 Thread J. Landman Gay
On 2/27/11 3:30 AM, Richmond wrote: Having made a jazzy cursor for my text field I am wondering if there is possibly a way where, after an insertion point has been decided on, the cursor can remain with the insertion point unless the user moves it. The problem is this: The user is jigging back

Cursed by insertions

2011-02-27 Thread Richmond
Having made a jazzy cursor for my text field I am wondering if there is possibly a way where, after an insertion point has been decided on, the cursor can remain with the insertion point unless the user moves it. The problem is this: The user is jigging back and forth between the textField in th