[M3devel] formsediit/macmodel problem

[Jay]

That's better, thanks!
I still have little idea what is going on here.
I can test it out a bit, can't vouch for it via code review,
at least not yet.

If you have multiple lines, of varying lengths..
not sure if this is due to word wrap or not,
and click in empty space past the end of one of the lines
and type, letters do not appear.

If you click at the end of the line ok.
I think clicking past the end of the line needs to pin the resulting
cursor location to the end of the line.

 I really don't know this code. :(
I think it was written by people who had implemented the same
things multiple times and by this time had all exactly in their head
just how to factor it perfectly for the right amount of flexibility.
"Right amount of flexibility" => "harder for newbies to understand.." :(
I need to read the green book and pay close attn the whole time. :)

I still get a sort of stray looking vertical red line when I first type after clicking.
But it can be deemed minor (depending on Randy's customer really).
Probably should focus on the pixmap problem.
Can I repro it on one machine???

Randy, you might want to try out the "emacs" model, perhaps it is better tested
and works ok. ?

 - Jay



> Date: Sun, 3 Aug 2008 11:44:54 +0000
> To: m3commit at elegosoft.com
> From: wagner at elego.de
> Subject: [M3commit] CVS Update: cm3
>
> CVSROOT: /usr/cvs
> Changes by: wagner at birch. 08/08/03 11:44:54
>
> Modified files:
> cm3/m3-ui/vbtkit/src/: m3overrides
> cm3/m3-ui/vbtkit/src/etext/: MacModel.m3 TextPort.m3
>
> Log message:
> tentative fix for text selection and insertion in the Mac TextPortModel:
>
> The strange behaviour reported by Randy Coleburn (mouse click, left, left,
> insert --> first character inserted at mouse click point) should now be gone;
> cursor up and down at the right end of ragged paragraphs still looks
> a bit strange, but that seems to be not worse than before. It still
> should be fixed though.
>
> These changes should be reviewed and tested by others; they seem to do
> the right thing for me, but I haven't done extensive testing, especially
> in other modes.
>