You either call KoTextEditor->beginEditBlock before doing all the
operations (ie, before deleting the shape and the anchor), and call
textEditor->endEditBlock(),
or alternatively you create a KUndo2Command and call
KoTextEditor->addCommand(yourCommand). I think the second method is better
as it all
On Wednesday, January 04, 2012 11:55:14 Boudewijn Rempt wrote:
> On Thursday 15 December 2011 Dec, Boudewijn Rempt wrote:
> > It turns out that currently, only the rdf system keeps the actual id
> > strings after loading is finished, the other parts of calligra only
> > use the id strings to build
On Thursday 15 December 2011 Dec, Boudewijn Rempt wrote:
> It turns out that currently, only the rdf system keeps the actual id
> strings after loading is finished, the other parts of calligra only
> use the id strings to build their mappings during loading, and
> recreate them during saving.
T
On Thursday 15 December 2011 Dec, Jos van den Oever wrote:
> I generally like the plan and could not find any problem. A question though:
> would the classes KoElementReferenceData know if there are any
> KoElementReference instances that point to it? If there aren't any, there is
> no need to
On Thursday, December 15, 2011 16:24:24 PM Boudewijn Rempt wrote:
> On Thursday 15 December 2011 Dec, Jos van den Oever wrote:
> > On Thursday, December 15, 2011 11:21:19 AM Thorsten Zachmann wrote:
> > > > Well, no... Not that I could find. In fact, until yesterday
> > > > encountering an xml:id w
On Thursday 15 December 2011 16:24:24 Boudewijn Rempt wrote:
> In passing: it would be good if we could directly attach rdf metadata to an
> element (like text:table) instead of always having to work with bookmarks.
Yes very. Bookmarks, anchors and softbreaks are evil in that they are are non
visi
On Thursday 15 December 2011 Dec, Jos van den Oever wrote:
> On Thursday, December 15, 2011 11:21:19 AM Thorsten Zachmann wrote:
> > > Well, no... Not that I could find. In fact, until yesterday encountering
> > > an xml:id when loading text or bookmarks always means "aha! rdf!", and
> > > the load
On Thursday, December 15, 2011 11:21:19 AM Thorsten Zachmann wrote:
> > Well, no... Not that I could find. In fact, until yesterday encountering
> > an xml:id when loading text or bookmarks always means "aha! rdf!", and
> > the loading code doesn't have access to the rdf document, which it could
>
On Thursday, December 15, 2011 10:38:42 Boudewijn Rempt wrote:
> On Thursday 15 December 2011 Dec, Thorsten Zachmann wrote:
> > On Thursday, December 15, 2011 09:14:28 Boudewijn Rempt wrote:
> > > On Thursday 15 December 2011 Dec, Thorsten Zachmann wrote:
> > > > for me this looks like a bit of ove
On Thursday 15 December 2011 Dec, Thorsten Zachmann wrote:
> On Thursday, December 15, 2011 09:14:28 Boudewijn Rempt wrote:
> > On Thursday 15 December 2011 Dec, Thorsten Zachmann wrote:
> > > for me this looks like a bit of overkill. Let me explain how the id stuff
> > > in the animations work.
>
On Thursday, December 15, 2011 09:14:28 Boudewijn Rempt wrote:
> On Thursday 15 December 2011 Dec, Thorsten Zachmann wrote:
> > for me this looks like a bit of overkill. Let me explain how the id stuff
> > in the animations work.
>
> Right now, for animations, draw:id is used, isn't it?
right but
On Thursday 15 December 2011 Dec, Thorsten Zachmann wrote:
> for me this looks like a bit of overkill. Let me explain how the id stuff in
> the animations work.
Right now, for animations, draw:id is used, isn't it?
> The xml id is not kept. It is only used during loading to
> be able to get t
Hello,
On Wednesday, December 14, 2011 16:21:53 Boudewijn Rempt wrote:
> On Wednesday 14 December 2011 Dec, C. Boemann wrote:
> > all well, except how do the animation framework get the related qobject
> > from this?
>
> I'm not sure how that works now, I guess they use the xml:id or draw:id as
>
On Wednesday 14 December 2011 Dec, C. Boemann wrote:
> all well, except how do the animation framework get the related qobject from
> this?
I'm not sure how that works now, I guess they use the xml:id or draw:id as a
qstring key into a map. So then it should use the reference, not the id string
On Wednesday 14 December 2011 16:06:15 Boudewijn Rempt wrote:
> On Wednesday 14 December 2011 Dec, Boudewijn Rempt wrote:
> > On Friday 02 December 2011 Dec, Jos van den Oever wrote:
> > > After upgrading the calligra source code to the latest version of the
> > > Relax NG schema, a problem became
On Wednesday 14 December 2011 Dec, Boudewijn Rempt wrote:
> On Friday 02 December 2011 Dec, Jos van den Oever wrote:
> > After upgrading the calligra source code to the latest version of the Relax
> > NG
> > schema, a problem became apparent.
> >
> > In various places, Calligra uses text:id. In
On Friday 02 December 2011 Dec, Jos van den Oever wrote:
> After upgrading the calligra source code to the latest version of the Relax
> NG
> schema, a problem became apparent.
>
> In various places, Calligra uses text:id. In ODF 1.2, text:id has been
> deprecated in many places in favor of xml
On Friday, December 02, 2011 16:38:29 PM Jos van den Oever wrote:
> After upgrading the calligra source code to the latest version of the Relax
> NG schema, a problem became apparent.
>
> In various places, Calligra uses text:id. In ODF 1.2, text:id has been
> deprecated in many places in favor of
After upgrading the calligra source code to the latest version of the Relax NG
schema, a problem became apparent.
In various places, Calligra uses text:id. In ODF 1.2, text:id has been
deprecated in many places in favor of xml:id. For the specification
says:
---
The text:id attribute speci
19 matches
Mail list logo
