Am 31.10.2010 17:42, schrieb Jürgen Spitzmüller:
We need Abdel's help here. He has imlemented the new Apply/OK scheme and
I'm sure he knows a solution. I mean it works for setting multicolumns so
it should work also for multirows using the same tabular UI<-> Inset
communication. Abdel?
As said, I'm not sure. The current communication method is a big, big cludge,
and it looks like multirow is bringing it at its limits.
When this is a problem wee need to hear Abdel's opinion first.
I currently see only the problem mentioned above now:
http://wiki.lyx.org/Devel/Multirow I think my patch doesn't increase the
complexity a lot -- the edit field is only used when a cell is multirow.
Have you tested my patch? Maybe I have overseen something and if you find
a bug or regression. Then I will of course agree with you it is better to
postpone. (Without testing it is like judging a book by its cover ;-) )
No, but note that if we do not manage to solve the tabular issues with
multirow before 2.0 (which is not unlikely), I will vote for deactivating
multirow support. We cannot ship a defect feature.
I'm not responsible for the new tabular Apply/OK scheme. As you say, the problem lies within this
scheme, we need to revert this scheme not aprticular table feature. We have much more new table
features that suffer from this scheme, see
http://www.lyx.org/trac/ticket/6997
I committed the multirow feature before the Apply scheme was introduced and are disappointed that
you see me guilty that multirow doesn't work yet perfectly with this scheme.
> But I've to admit, I agree more with Jürgen. Currently I cannot work on the
> buffer-info of VCS anymore because the InsetInfo dialog doesn't work anymore
because of the
> ASSERTs.
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?
regards Uwe
