Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 13-Jul-2000 Lars Gullik Bjønnes wrote:
| >|
| >| Well you need 1 LyXText per BufferView, that's already true because 1
| >| LyXText is the status of only 1 displayed version so what's the question
| >| here?
| >
| > Don't you use lyxtext inside the
On 13-Jul-2000 Lars Gullik Bjønnes wrote:
>|
>| Well you need 1 LyXText per BufferView, that's already true because 1
>| LyXText is the status of only 1 displayed version so what's the question
>| here?
>
> Don't you use lyxtext inside the insettext too?
Yes you're right, but that hasn't to do
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 13-Jul-2000 Lars Gullik Bjønnes wrote:
| >
| > So one locking inset for each LyXText?
| >
|
| Yes!
|
| > Almost like a focus variable?
| >
| > If you think that solve problems with insettext's etc. then try it.
| > How will that mix with multipl
On 13-Jul-2000 Lars Gullik Bjønnes wrote:
>
> So one locking inset for each LyXText?
>
Yes!
> Almost like a focus variable?
>
> If you think that solve problems with insettext's etc. then try it.
> How will that mix with multiple views of the same document?
Well you need 1 LyXText per Buffe
Juergen Vigna <[EMAIL PROTECTED]> writes:
| Hi!
|
| I've just seen that we have a problem if we change buffer and are inside
| an inset so that the_locking_inset in the BufferView is set. The problem
| is that we now have another LyXText visible in this BufferView which does
| not have that lock
Hi!
I've just seen that we have a problem if we change buffer and are inside
an inset so that the_locking_inset in the BufferView is set. The problem
is that we now have another LyXText visible in this BufferView which does
not have that locking_inset, but we still have that variable set and used
