Le 07/11/2020 à 16:52, Yuriy Skalko a écrit :
I never understood how it works, but I always assumed it was C++ for
grown ups, jut without the lambda function mess. All I can say is that
it works :)
JMarc
That's the most important thing, the rest are implementation details :)
Now I've found
I never understood how it works, but I always assumed it was C++ for grown ups,
jut without the lambda function mess. All I can say is that it works :)
JMarc
That's the most important thing, the rest are implementation details :)
Now I've found that Changer is just no-op variant of
Le 06/11/2020 à 23:53, Yuriy Skalko a écrit :
Yes, RefChanger is an interesting approach, it will be better than stack.
This NewOutputParams class looks like variation of the RefChanger. Right?
I understand how RefChanger works, but Changer is a strange thing. How
can it work with empty
On Sat, Nov 07, 2020 at 12:53:33AM +0200, Yuriy Skalko wrote:
> P.S. I've tried to search for some docs on Changers in LyX repository and
> found this useful document: development/coding/CodingRulesAndAdvice.lyx.
> Maybe it will be reasonable to merge it into lib/doc/Development.lyx so that
>
I started a patch some time ago trying something like that method for
OutputParams generally. The destuctor for the new instance copied relevant
changes back to the one one. Basically something like:
class NewOutputParams : public OutputParams {
explicit NewOutputParams(OutputParams
be
propagated on the higher level.
Or use Changers.
I started a patch some time ago trying something like that method for
OutputParams generally. The destuctor for the new instance copied
relevant changes back to the one one. Basically something like:
class NewOutputParams : public
Le 06/11/2020 à 10:57, Yuriy Skalko a écrit :
And to implement for OutputContext the push/pop operations (with
internal stack) to save/restore parent context (when needed to do local
changes) or directly modify parent context if changes should be
propagated on the higher level.
Or use
Yes, I looked at it but didn't have time then to comment.
It's fine as far as it goes, but I was thinking something somewhat different.
Others can chime in, perhaps, but I think there's a reason that OutputParams
was always supposed to be passed as const. At least, it began life as precisely
at it but didn't have time then to comment.
It's fine as far as it goes, but I was thinking something somewhat
different. Others can chime in, perhaps, but I think there's a reason
that OutputParams was always supposed to be passed as const. At least,
it began life as precisely what it sounds like: A bunch
Dear LyX Developers,
I'm trying to add a simple list objet to the OutputParams header file, but I
keep getting strange errors and I can't figure out what's causing them.
Here's what I would like to do:
#include list
#include insets/InsetFoot.h
...
std::listInsetFoot const * footlist;
However
Dear LyX Developers,
I'm trying to add a simple list objet to the OutputParams header file, but I
keep getting strange errors and I can't figure out what's causing them.
Here's what I would like to do:
#include
#include
...
std::list footlist;
However, I can't get that far. When I include
On Thu, Apr 21, 2011 at 08:22:05PM -0400, Richard Heck wrote:
Not that I'm intending to commit this soon, but I thought I'd post
this patch now for comment and commit shortly after 2.0. This patch
un-mutables most of the mutable members of OutputParams. A couple
remain: encoding, which maybe
of OutputParams. A couple
remain: encoding, which maybe should be mutable, and inulemcmd,
which I'm less sure about, though maybe it should be too. Anyway,
comments welcome.
You don't explain the logic of your patch. A quick glance (I have no time
right now to go deeply into it) seems to suggest that you
On Thu, Apr 21, 2011 at 08:22:05PM -0400, Richard Heck wrote:
> Not that I'm intending to commit this soon, but I thought I'd post
> this patch now for comment and commit shortly after 2.0. This patch
> un-mutables most of the mutable members of OutputParams. A couple
> remain: enc
of OutputParams. A couple
remain: encoding, which maybe should be mutable, and inulemcmd,
which I'm less sure about, though maybe it should be too. Anyway,
comments welcome.
You don't explain the logic of your patch. A quick glance (I have no time
right now to go deeply into it) seems to suggest that you
Not that I'm intending to commit this soon, but I thought I'd post this
patch now for comment and commit shortly after 2.0. This patch
un-mutables most of the mutable members of OutputParams. A couple
remain: encoding, which maybe should be mutable, and inulemcmd, which
I'm less sure about
Not that I'm intending to commit this soon, but I thought I'd post this
patch now for comment and commit shortly after 2.0. This patch
un-mutables most of the mutable members of OutputParams. A couple
remain: encoding, which maybe should be mutable, and inulemcmd, which
I'm less sure about
17 matches
Mail list logo
