FROM : Max Seelemann
DATE : Fri Apr 01 14:59:41 2005
Hi Keith,
Yes I did so. The demo application I sent to Apple was just equipped
with one textview and all the stuff around. One of the movies showed
this application. I think it's this one:
<http://www.blue-tec.com/private/stuff/snapshot2.mov>. So after few
further optimizations I found out something very interesting: I'm
unable to reproduce the effects from the movie in the same application.
Somehow after implementing these optimizations in the splitview with
two textviews the old behaviour is back. So I can second this behaviour
more or less.
Rewriting is - for now - out of my range. I spent very much time on
this thing and to get it work as it should was quite a bit of work. I'm
still optimizing here and there and find new ways to make it faster but
the problem stays.
Your thought that two textviews using the same storage may cause
problems is very interesting to me. I'm thinking about doing some kind
of "forwarded" textstorage that consists of a central store but every
textview has its own textstorage that gets its content from the central
one. This might solve the problems. Sometimes I also need to connect a
third textstorage and this would make it much easier I think...
Thank you for your thoughts they're very appreciated.
Max
DATE : Fri Apr 01 14:59:41 2005
Hi Keith,
Yes I did so. The demo application I sent to Apple was just equipped
with one textview and all the stuff around. One of the movies showed
this application. I think it's this one:
<http://www.blue-tec.com/private/stuff/snapshot2.mov>. So after few
further optimizations I found out something very interesting: I'm
unable to reproduce the effects from the movie in the same application.
Somehow after implementing these optimizations in the splitview with
two textviews the old behaviour is back. So I can second this behaviour
more or less.
Rewriting is - for now - out of my range. I spent very much time on
this thing and to get it work as it should was quite a bit of work. I'm
still optimizing here and there and find new ways to make it faster but
the problem stays.
Your thought that two textviews using the same storage may cause
problems is very interesting to me. I'm thinking about doing some kind
of "forwarded" textstorage that consists of a central store but every
textview has its own textstorage that gets its content from the central
one. This might solve the problems. Sometimes I also need to connect a
third textstorage and this would make it much easier I think...
Thank you for your thoughts they're very appreciated.
Max
| Related mails | Author | Date |
|---|---|---|
| Marcus Fehn | Mar 25, 20:49 | |
| Finlay Dobbie | Mar 25, 21:24 | |
| todd ransom | Mar 25, 21:32 | |
| Chaz McGarvey | Mar 26, 09:15 | |
| Kay Roepke | Mar 27, 19:53 | |
| Marcus Fehn | Mar 27, 21:43 | |
| Ryan Stevens | Mar 27, 22:38 | |
| Max Seelemann | Mar 28, 21:02 | |
| Ryan Stevens | Mar 29, 03:21 | |
| Bob Ippolito | Mar 29, 04:01 | |
| Max Seelemann | Mar 31, 17:53 | |
| Max Seelemann | Mar 31, 17:57 | |
| Keith Blount | Mar 31, 21:28 | |
| Sascha Matzke | Apr 1, 10:53 | |
| Max Seelemann | Apr 1, 14:59 |






Cocoa mail archive

