Edwin Leuven wrote:
i've noticed that breaking a paragraph is much quicker than unbreaking
it (cursor at beginning of par and then backspace)
i think that this has always been the case, but i was wondering whether
there is something that can be done about it? (i guess i am looking at
you
Abdelrazak Younes [EMAIL PROTECTED] writes:
| private:
| ///
| string lang_;
| + typedef std::mapstring, docstring CacheType;
| + /// Internal cache for gettext translated strings.
| + /// This is needed for performance reason within \c updateLabels()
| + /// under
Lars Gullik Bjønnes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
| private:
| ///
| string lang_;
| + typedef std::mapstring, docstring CacheType;
| + /// Internal cache for gettext translated strings.
| + /// This is needed for performance reason within \c
Edwin Leuven wrote:
i've noticed that breaking a paragraph is much quicker than "unbreaking"
it (cursor at beginning of par and then backspace)
i think that this has always been the case, but i was wondering whether
there is something that can be done about it? (i guess i am looking at
you
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| private:
| ///
| string lang_;
| + typedef std::map CacheType;
| + /// Internal cache for gettext translated strings.
| + /// This is needed for performance reason within \c updateLabels()
| + ///
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| private:
| ///
| string lang_;
| + typedef std::map CacheType;
| + /// Internal cache for gettext translated strings.
| + /// This is needed for performance reason within \c
i've noticed that breaking a paragraph is much quicker than unbreaking
it (cursor at beginning of par and then backspace)
i think that this has always been the case, but i was wondering whether
there is something that can be done about it? (i guess i am looking at
you abdel ;-)
and of
Edwin Leuven wrote:
i've noticed that breaking a paragraph is much quicker than unbreaking
it (cursor at beginning of par and then backspace)
i think that this has always been the case,
Actually, breaking a paragraph has been optimized when within a
non-numbered layout (look at the
i've noticed that breaking a paragraph is much quicker than "unbreaking"
it (cursor at beginning of par and then backspace)
i think that this has always been the case, but i was wondering whether
there is something that can be done about it? (i guess i am looking at
you abdel ;-)
and of
Edwin Leuven wrote:
i've noticed that breaking a paragraph is much quicker than "unbreaking"
it (cursor at beginning of par and then backspace)
i think that this has always been the case,
Actually, breaking a paragraph has been optimized when within a
non-numbered layout (look at the
10 matches
Mail list logo