On 01/11/2010 19:15, Uwe Stöhr wrote:
Am 01.11.2010 18:19, schrieb Abdelrazak Younes:
Did I respond?
Not yet ;-)
The problem in #6997 is not a general issue, it is just a problem
with the table dialog because we
don't read the full table parameters each time we move. So that is a
bug and it is fixable. But as
Juergen said elsewhere this is difficult to solve because the table
parameters are difficult to
localize, unlike InsetParms based dialog for example.
The problem is that the immediate apply option also applies when
switching to another table.
This is intended. The problem is not here.
If this cannot be fixed easily I can sanitize the few cases where this
leads to problems like switching from/to longtable and normal table
(the one I described in the bug report).
I have not checked by it seems to me that the dialog status for
longtable is not correctly updated when switching between the two
tables. This doesn't seem hard to solve.
But before I start working on that I wanted to hear your opinion if
there is another solution.
Just verify that all table parameters (including longtable) are
correctly handled in paramsToDialog().
[...]
>> It seems that we have a general problem of getting the code
stabilized. Wouldn't it therefore be
>> better to postpone things like the migration of dialogs to
InsetParamsDialog until the current
>> dialog issues are sorted out?
>
> Oh, I am only trying to offer a consistent look&feel for LyX-2.0,
that's all. But I don't think I > destabilize the code a lot... At
least I know I can fix things in case I break them.
Then everything is fine. However I'm not sure if you manage to migrate
all dialogs for LyX 2.0 or if we need to extend the release until the
migration is done and all dialogs are tested. This should be discussed
with Pavel.
Oh I only wanted to migrate 2 or 3 more dialogs (Citation Nomencl and
another one that I forgot).
Abdel.
