MantisBT - ParaView |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0015379 | ParaView | (No Category) | public | 2015-03-13 13:01 | 2016-08-12 09:59 |
|
Reporter | Alan Scott | |
Assigned To | Cory Quammen | |
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | moved | |
Platform | | OS | | OS Version | |
Product Version | | |
Target Version | 5.1 | Fixed in Version | | |
Project | Sandia |
Topic Name | |
Type | incorrect functionality |
|
Summary | 0015379: Color legend annotation font controls broken |
Description | I have users that are splitting the view horizontally a few times, and cannot get the color legend annotation font large enough to be useful. This needs to be fixed.
* 4.3.1, Linux, local server.
* Sources/ Wavelet. Apply. Representation Surface. Color by RTData.
* Enable the color editor.
* Split view horizontally. Split right view horizontally. (You may need to split one more time. This issue is screen dependent, and I am working on a small screen.)
<<Bug>> pull the color legend out where you can see it. Notice the fonts are tiny. Go to the color legend editor, try to increase the size of the font. It won't increase. But it should - even if it falls outside of the view. Please change this. |
Steps To Reproduce | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | 0015637 | closed | Kitware Robot | Color legend annotation mode is wrong size for short windows |
|
Attached Files | bugStillExists.png (218,277) 2015-09-02 15:54 https://www.vtk.org/Bug/file/9897/bugStillExists.png
|
|
Issue History |
Date Modified | Username | Field | Change |
2015-03-13 13:01 | Alan Scott | New Issue | |
2015-03-13 14:20 | Alan Scott | Target Version | => 4.4 |
2015-06-08 14:27 | Utkarsh Ayachit | Assigned To | => David C. Lonie |
2015-06-08 14:28 | Utkarsh Ayachit | Status | backlog => todo |
2015-06-24 13:16 | David C. Lonie | Note Added: 0034607 | |
2015-06-24 13:16 | David C. Lonie | Status | todo => active development |
2015-06-25 15:20 | David C. Lonie | Note Added: 0034610 | |
2015-07-22 12:16 | David C. Lonie | Note Added: 0034812 | |
2015-07-22 12:16 | David C. Lonie | Assigned To | David C. Lonie => Utkarsh Ayachit |
2015-08-13 17:09 | Cory Quammen | Note Added: 0034994 | |
2015-08-24 09:29 | Cory Quammen | Note Added: 0035040 | |
2015-09-02 15:54 | Utkarsh Ayachit | File Added: bugStillExists.png | |
2015-09-02 15:54 | Utkarsh Ayachit | Note Added: 0035131 | |
2015-09-02 16:05 | Cory Quammen | Note Added: 0035132 | |
2015-09-08 11:32 | Utkarsh Ayachit | Relationship added | related to 0015637 |
2015-09-11 16:43 | Utkarsh Ayachit | Target Version | 4.4 => 5.1 |
2016-03-03 11:23 | Utkarsh Ayachit | Assigned To | Utkarsh Ayachit => Cory Quammen |
2016-08-12 09:59 | Kitware Robot | Note Added: 0038787 | |
2016-08-12 09:59 | Kitware Robot | Status | active development => closed |
2016-08-12 09:59 | Kitware Robot | Resolution | open => moved |
Notes |
|
(0034607)
|
David C. Lonie
|
2015-06-24 13:16
|
|
Going to address this by:
1) Removing the "Maximum number of labels" option from the scalarbar.
2) Removing the font scaling bits to fix the font at the requested size. |
|
|
(0034610)
|
David C. Lonie
|
2015-06-25 15:20
|
|
|
|
(0034812)
|
David C. Lonie
|
2015-07-22 12:16
|
|
|
|
(0034994)
|
Cory Quammen
|
2015-08-13 17:09
|
|
|
|
(0035040)
|
Cory Quammen
|
2015-08-24 09:29
|
|
|
|
(0035131)
|
Utkarsh Ayachit
|
2015-09-02 15:54
|
|
Cory, I don't think !295 addresses this issue. See attached image. Note the scalar bar's labels are much smaller in view 2 and 3. |
|
|
(0035132)
|
Cory Quammen
|
2015-09-02 16:05
|
|
Indeed. It looks like the width of the scalar bar decreases with the width of the render view, and that constrains the font size. What we need is a way to fix that width, but the width is automatically calculated based on the render view width. I'm concerned that changing to a fixed-width mode will cause other problems, though. |
|
|
(0038787)
|
Kitware Robot
|
2016-08-12 09:59
|
|
Resolving issue as `moved`.
This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page. |
|