John Levon wrote:
Juergen, can you help ? What would you say if I suggest ripping the font
paramter from inset-update ?
I would say this could be a good idea. Just define a default font
for an empty CellInset and pass that one instead. IMO this is the best
solution and you're able to rip out the
John Levon wrote:
HA ! That's a bloody joke. This doesn't work. I have absolutely no idea
why, of course. This update stuff is entirely beyond understanding. Just
dealing with the bv-updateInset() vs. bv-update() vs. bv-update(blah)
vs. inset-update() vs. inset-updateInsetInInset() vs
On Wed, Mar 19, 2003 at 09:35:15PM +, John Levon wrote:
So it's looking very much like Andre's two-stage thingy at this point,
just to solve a tiny bit of this :(
Alejandro's two-stage thingy.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do
On Thu, Mar 20, 2003 at 03:06:48AM +, John Levon wrote:
On Wed, Mar 19, 2003 at 09:35:15PM +, John Levon wrote:
This is fun. Insets like InsetMinipage and InsetERT can have e.g.
INSET_MODIFY applied to them. This can actually alter its size. It
actually needs to tell its contained
On Thu, Mar 20, 2003 at 09:27:59AM +0100, Juergen Vigna wrote:
I would have been *really* surprised if you would have figured out a
better way in one day, do you know how long I worked on this stuff to
make it work as it is now.
heh :))
At this stage I just want to understand the basics
On Thu, Mar 20, 2003 at 09:32:01AM +0100, Andre Poenitz wrote:
HA ! That's a bloody joke. This doesn't work. I have absolutely no idea
why, of course. This update stuff is entirely beyond understanding.
But a two-stage approach is, isn't it?
Andre, how do you possibly expect me to be able
John Levon wrote:
Well, can you explain why calling insettext-update(reinit == true)
inside the insetminipage thing doesn't work ? That's alll I want to know
and after about 50 printf's, I'm still stuck.
Because you do it at the wrong spot! Try to printf x() and then after
it drawed it wrong (or
On Thu, Mar 20, 2003 at 04:19:02PM +0100, Juergen Vigna wrote:
Well, can you explain why calling insettext-update(reinit == true)
inside the insetminipage thing doesn't work ? That's alll I want to know
and after about 50 printf's, I'm still stuck.
Because you do it at the wrong spot!
Why
John Levon wrote:
Why is it the wrong spot ? Can you explain in simple terms ?
I explained below, the x position is changing during draw and if that
happens we have to recalculate all!
Dude, I spent *hours* doing this, and could not see where or why it
didn't work. This is lots of printfs in
On Thu, Mar 20, 2003 at 05:30:23PM +0100, Juergen Vigna wrote:
Draw + x()!
Ohh, Inset::x() ! Right ... which types of insettext actually care about
their x() position ? As I mentioned in my other mail + patch, a simple
test of a few scenarios couldn't cause any trouble
Only hours come on
John Levon wrote:
Juergen, can you help ? What would you say if I suggest ripping the font
paramter from inset->update ?
I would say this could be a good idea. Just define a "default" font
for an empty CellInset and pass that one instead. IMO this is the best
solution and you're able to rip out
John Levon wrote:
HA ! That's a bloody joke. This doesn't work. I have absolutely no idea
why, of course. This update stuff is entirely beyond understanding. Just
dealing with the bv->updateInset() vs. bv->update() vs. bv->update(blah)
vs. inset->update() vs. inset->updateInsetInInset() vs
On Wed, Mar 19, 2003 at 09:35:15PM +, John Levon wrote:
> So it's looking very much like Andre's two-stage thingy at this point,
> just to solve a tiny bit of this :(
"Alejandro's two-stage thingy".
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor
On Thu, Mar 20, 2003 at 03:06:48AM +, John Levon wrote:
> On Wed, Mar 19, 2003 at 09:35:15PM +, John Levon wrote:
>
> > This is fun. Insets like InsetMinipage and InsetERT can have e.g.
> > INSET_MODIFY applied to them. This can actually alter its size. It
> > actually needs to tell its
On Thu, Mar 20, 2003 at 09:27:59AM +0100, Juergen Vigna wrote:
> I would have been *really* surprised if you would have figured out a
> better way in one day, do you know how long I worked on this stuff to
> make it work as it is now.
heh :))
At this stage I just want to understand the basics
On Thu, Mar 20, 2003 at 09:32:01AM +0100, Andre Poenitz wrote:
> > HA ! That's a bloody joke. This doesn't work. I have absolutely no idea
> > why, of course. This update stuff is entirely beyond understanding.
>
> But a two-stage approach is, isn't it?
Andre, how do you possibly expect me to
John Levon wrote:
Well, can you explain why calling insettext->update(reinit == true)
inside the insetminipage thing doesn't work ? That's alll I want to know
and after about 50 printf's, I'm still stuck.
Because you do it at the wrong spot! Try to "printf x()" and then after
it drawed it wrong
On Thu, Mar 20, 2003 at 04:19:02PM +0100, Juergen Vigna wrote:
> >Well, can you explain why calling insettext->update(reinit == true)
> >inside the insetminipage thing doesn't work ? That's alll I want to know
> >and after about 50 printf's, I'm still stuck.
>
> Because you do it at the wrong
John Levon wrote:
Why is it the wrong spot ? Can you explain in simple terms ?
I explained below, the x position is changing during draw and if that
happens we have to "recalculate all"!
Dude, I spent *hours* doing this, and could not see where or why it
didn't work. This is lots of printfs in
On Thu, Mar 20, 2003 at 05:30:23PM +0100, Juergen Vigna wrote:
> Draw + x()!
Ohh, Inset::x() ! Right ... which types of insettext actually care about
their x() position ? As I mentioned in my other mail + patch, a simple
test of a few scenarios couldn't cause any "trouble"
> Only hours come on
Are we agreed that removing CHANGED_IN_DRAW is a good idea ? I believe
so.
This is fun. Insets like InsetMinipage and InsetERT can have e.g.
INSET_MODIFY applied to them. This can actually alter its size. It
actually needs to tell its contained InsetText to -update(reinit ==
true);
The old way
On Wed, Mar 19, 2003 at 09:35:15PM +, John Levon wrote:
This is fun. Insets like InsetMinipage and InsetERT can have e.g.
INSET_MODIFY applied to them. This can actually alter its size. It
actually needs to tell its contained InsetText to -update(reinit ==
true);
HA ! That's a bloody
Are we agreed that removing CHANGED_IN_DRAW is a good idea ? I believe
so.
This is fun. Insets like InsetMinipage and InsetERT can have e.g.
INSET_MODIFY applied to them. This can actually alter its size. It
actually needs to tell its contained InsetText to ->update(reinit ==
true);
The "old
On Wed, Mar 19, 2003 at 09:35:15PM +, John Levon wrote:
> This is fun. Insets like InsetMinipage and InsetERT can have e.g.
> INSET_MODIFY applied to them. This can actually alter its size. It
> actually needs to tell its contained InsetText to ->update(reinit ==
> true);
HA ! That's a
24 matches
Mail list logo
