Issue 31541 - Merged missmatched tables columns aren't standisable
Summary: Merged missmatched tables columns aren't standisable
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.1.2
Hardware: All Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 31842 116815 (view as issue list)
Depends on:
Blocks:
 
Reported: 2004-07-15 16:25 UTC by cheesemp
Modified: 2013-08-07 14:38 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Shows two merged table. One that can't be standised (6.23 KB, application/vnd.sun.xml.writer)
2004-07-15 16:26 UTC, cheesemp
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description cheesemp 2004-07-15 16:25:08 UTC
When you merge two or more tables with columns of different width/positions you
are unable with the mouse to make a column a consistent size for all cells.

You can get round this by manually set cell width but why does OO refuse to let
me make them the same size by mouse (or any icons that I can find)?
Comment 1 cheesemp 2004-07-15 16:26:05 UTC
Created attachment 16489 [details]
Shows two merged table. One that can't be standised
Comment 2 michael.ruess 2004-07-21 10:47:34 UTC
MRU->AMA: I don't if this is more a defect or an enhancement... but it's true,
that we somehow need a possibility to align such columns to a matching width.
Comment 3 michael.ruess 2004-07-21 15:59:25 UTC
*** Issue 31842 has been marked as a duplicate of this issue. ***
Comment 4 cheesemp 2004-07-21 16:30:06 UTC
I'd feel it is a defect as you can sort this out by manually setting cell widths
(but thats slow) but you cant sort this out with the mouse which can't be right!

Also i've just seen I've marked my version as 1.0.2, its not its 1.1.2. Dont
expect it makes any difference just want to make things clear.
Comment 5 eric.savary 2011-02-04 19:35:18 UTC
*** Issue 116815 has been marked as a duplicate of this issue. ***