[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Some input on tables
From:       Elvis Stansvik <elvstone () gmail ! com>
Date:       2009-06-15 10:47:34
Message-ID: 751a4f870906150347v6ed2b740rba5c0c7749108b53 () mail ! gmail ! com
[Download RAW message or body]

2009/6/15 Thomas Zander <zander@kde.org>:
> On Monday 15. June 2009 12.34.44 Elvis Stansvik wrote:
>> > Just to add some input: we decided to create an "editor" interface to the
>> > QTextDocument in each frame. This interface will wrap the QTextCursor up,
>> > making sure undo/redo and changeTracking is properly taken care of. This
>> > means that manipulating the QTextCursor directly should be avoided. This
>>
>> Hm. I see. Is this something that is currently in SVN? I kind of have
>> to get on with my work, and I see QTextCursor used quite liberally in
>> Layout.cpp. And at the moment I'm not working on editing at all, just
>> trying to do some initial layout of tables, so nothing that should end
>> up on undo/redo/changetracking AFAICS. E.g. I'm only working at the
>> layout part of it at the moment.
>
> The code that you work on will likely never actually change the document, so
> going to the editor that Pierre is working on is not needed.
>
> Pierre; the QTextCursor usage that Elvis is talking about is purely for read-
> only purposes. I.e. Figure out if a block is in a table etc.

Yep. That's what I was thinking too, it's basically just temporary QTextCursors.

>
> I think both your work is not interfering with each other for quite some time
> to come :)

I'll do my best to make that as short time as possible! ;)

Elvis

> --
> Thomas Zander
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]