On Thu, Nov 02, 2006 at 12:37:41PM +1800, Bo Peng wrote:
> >> The major problem is with
> >> math/review/table toolbars. The logic is now:
> >>
> >> 1. if math is on when lyx exists, I assume it is always on
> >> 2. if math is off when lyx exists, I assume it is auto.
> >
> >But now it does not rem
> I think we are not going to do anything useful without intercepting
> the Qt toolbars popup and using ours instead. Then the session code
> will have real data to look at, not some randomly relevant values from
> Qt.
This is Bo's latest suggestion if I understand it correctly.
So the menu is
Bo Peng wrote:
I am sorry but where this menu is implemented? I can not find it
anywhere. I need to either change it to
review -> on/off/auto (submenu)
A submenu is the best option in my opinion. The menu is created by Qt
and should be replaced with a custom menu.
Joost
Jean-Marc Lasgouttes wrote:
I think we are not going to do anything useful without intercepting
the Qt toolbars popup and using ours instead. Then the session code
will have real data to look at, not some randomly relevant values from
Qt.
This is Bo's latest suggestion if I understand it correc
On Wednesday 01 November 2006 8:00 pm, Jean-Marc Lasgouttes wrote:
> Well, the initial settings are useful.
I agree.
> JMarc
--
José Abílio
Jean-Marc Lasgouttes wrote:
Well, the initial settings are useful.
Indeed, it should be possible to set the state when a user starts LyX
for the first time.
Joost
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
>> Depending on these two states the mode can be set to 'on', 'off' or
>> 'auto'.
Bo> The problem is how you switch them through right-click-menu, and
Bo> how to differentiate the states when lyx exits?
I think we are not going to do anything usef
> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:
Michael> In other words: Once the settings are saved, the default.ui
Michael> settings are pointless. Which suggests getting rid of them.
Well, the initial settings are useful.
JMarc
At the same time this menu should also be accessible using View >
Toolsbars. Otherwise there is a problem when all toolbars are hidden.
I am sorry but where this menu is implemented? I can not find it
anywhere. I need to either change it to
review -> on/off/auto (submenu)
or
X review
X auto rev
> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:
Michael> With the proposed solution above, "auto" is silently
Michael> introduced, even if the user doesn't like it. I am willing to
Michael> accept this for math and table but not for review.
That is the problem: everybody has his own
Bo Peng wrote:
1. we modify the right-click-menu to (use review, math, table are the same)
X review (on/off)
X auto review (on/off)
autoreview will override on/off. That is to say, we default to review
(always) on, or (always) off. It a user select auto review, then auto
is enabled. The mode s
There is no problem. You can save a different state depending on whether
the user is working in text mode or math mode.
This is difficult.
Maybe:
1. we modify the right-click-menu to (use review, math, table are the same)
X review (on/off)
X auto review (on/off)
autoreview will override on/
Peter Kümmel wrote:
Now is the time to discuss. ;)
We have two possibilities:
1. default is context-sensitive but the manual change to show
when the CT toolbar is hidden will be rememberd forever
2. default is visible and hiding moves the toolbar to the context-sensitive
state
There are
Bo Peng wrote:
The problem is how you switch them through right-click-menu, and how
to differentiate the states when lyx exits?
There is no problem. You can save a different state depending on whether
the user is working in text mode or math mode. If you remember these two
states it is also p
Depending on these two states the mode can be set to 'on', 'off' or 'auto'.
The problem is how you switch them through right-click-menu, and how
to differentiate the states when lyx exits?
Bo
Bo Peng wrote:
>> > The major problem is with
>> > math/review/table toolbars. The logic is now:
>> >
>> > 1. if math is on when lyx exists, I assume it is always on
>> > 2. if math is off when lyx exists, I assume it is auto.
>>
>> But now it does not remember the position of the moved auto toolba
> 1. if math is on when lyx exists, I assume it is always on
> 2. if math is off when lyx exists, I assume it is auto.
Will it be the same with "review"? Yesterday, I noticed that
context-sensitive toolbars can be a real pain. Just imagine two loaded
documents, one with CT on, the other one with
Peter Kümmel wrote:
We have two possibilities:
1. default is context-sensitive but the manual change to show
when the CT toolbar is hidden will be rememberd forever
2. default is visible and hiding moves the toolbar to the context-sensitive
state
No, it is also possible to save multiple st
Bo Peng wrote:
The logic is now:
1. if math is on when lyx exists, I assume it is always on
2. if math is off when lyx exists, I assume it is auto.
I don't think this is a good idea. Either multiple states should be
saved (on/off in text mode and on/off in math mode) or the auto toolbars
sho
> The major problem is with
> math/review/table toolbars. The logic is now:
>
> 1. if math is on when lyx exists, I assume it is always on
> 2. if math is off when lyx exists, I assume it is auto.
But now it does not remember the position of the moved auto toolbars.
Because auto toolbars are no
Michael Gerz wrote:
> Bo Peng wrote:
>
>> 1. if math is on when lyx exists, I assume it is always on
>> 2. if math is off when lyx exists, I assume it is auto.
>
> Will it be the same with "review"? Yesterday, I noticed that
> context-sensitive toolbars can be a real pain. Just imagine two loaded
On Wed, Nov 01, 2006 at 07:28:09PM +0100, Michael Gerz wrote:
> >1. if math is on when lyx exists, I assume it is always on
> >2. if math is off when lyx exists, I assume it is auto.
>
> Will it be the same with "review"? Yesterday, I noticed that
> context-sensitive toolbars can be a real pain.
Michael Gerz wrote:
How do the session settings and the default settings in default.ui
interact? Which overrules which?
And do we still need default settings in default.ui at all?
I assume they are obsolete after the first startup, because then the
session info overrule the default.ui settin
Bo Peng wrote:
> Hi, Peter,
>
> I revised your patch and now it works fine (save restore on/off and
Nice improvements! I feared the casts.
> location). It works like this. The major problem is with
> math/review/table toolbars. The logic is now:
>
> 1. if math is on when lyx exists, I assume it
Bo Peng wrote:
1. if math is on when lyx exists, I assume it is always on
2. if math is off when lyx exists, I assume it is auto.
Will it be the same with "review"? Yesterday, I noticed that
context-sensitive toolbars can be a real pain. Just imagine two loaded
documents, one with CT on, the
It works like this. The major problem is The logic is now:
I surely wrote something more readable, but gmail messed things up
when it stopped responding and I clicked "send" the second time. I
have also checked my system time, and it is accurate to milliseconds.
I guess the gmail SMTP serv
Hi, Peter,
I revised your patch and now it works fine (save restore on/off and
location). It works like this. The major problem is with
math/review/table toolbars. The logic is now:
1. if math is on when lyx exists, I assume it is always on
2. if math is off when lyx exists, I assume it is auto.
27 matches
Mail list logo
