Leuven, E. wrote: > Georg Baum wrote: >> Another one is the "single >> cell multicolumn" problem: The fact that you need \multicolumn if you >> want to change the alignment or border of just one cell is a LaTeX >> implementation issue, and the user should not need to know that. LyX >> should create multicolumn cells automatically if needed. > > and what about tricks like setting multicolumn on single cells to > circumvene decimal alignment by dcolumn?
It should of course be possible to set a 1-cell multicolumn explicitly if that is needed, because you can never imagine all the tricks that users might need. But this is expert usage, normally you should not need to think about it. >> I believe that you can simplify the tabular code a lot if you go away >> from the LaTeX-centric view and implement a more general table model. All >> the special LaTeX stuff would then be concentrated in the LaTeX export >> methods. > > ok (but perhaps some latex "tricks" are then no longer feasible?) What do you have in mind? This should of course be avoided, but I don't see how a more general table model in LyX would create problems with LaTeX tricks. >> Of course it should still be possible to easily set/unset borders of >> whole rows/columns, but that is orthogonal to the way how the lines are >> stored. > > yes, we should make it easy to select complete rows/columns after whcih we > can apply our methods on the cell range... Exactly. This works partially already. Georg
