View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004315 | FreeCAD | Feature | public | 2020-04-15 16:23 | 2022-02-04 19:49 |
Reporter | fc_tofu | Assigned To | |||
Priority | low | Severity | minor | Reproducibility | have not tried |
Status | acknowledged | Resolution | open | ||
Target Version | 0.20 | ||||
Summary | 0004315: FEM WB, WarpVector widget default position from Right to Left | ||||
Description | By default pref, NaviCube shows on TopRight corner of viewport, and WarpVector bar widget (FEM WB) cannot be moved. NaviCube and WarpVector bar widget overlay at TopRight corner in every new installed FreeCAD. A known workgound is to move NaviCube away to the left. But right side of viewport is more "stable" and preferable. By "stable", I mean that cannot be affected by frequent ajustment of neighboring ComboView border position. Since NaviCube is far more used than WarpVector bar, so I hope the NaviCube can stay at right, and WarpVector bar moved to left as future default position. To prevent new conflict with other/potential widgets, a "Alighment = Left/Right" option can be added to view properties of WarpVector. | ||||
Steps To Reproduce | Open stock example file "FemCalculixCantilever3D.FCStd", then WarpVector bar widget appear on right of viewport with NaviCube overlayed on TopRight corner. | ||||
Additional Information | Forum discussion | ||||
Tags | #ready-for-migration | ||||
FreeCAD Information | OS: Windows 10 (10.0) Word size of OS: 64-bit Word size of FreeCAD: 64-bit Version: 0.19.20514 (Git) Build type: Release Branch: master Hash: a05ffd499366ab12fa1b43f37db73f4f1e9c332d Python version: 3.8.2 Qt version: 5.12.5 Coin version: 4.0.0 OCC version: 7.4.0 Locale: Chinese/China (zh_CN) | ||||
|
@jnxd can you take a look at this ? |
|
|
|
Thanks for locating the exact place where the colorbar is implemented. Unfortunately there's no clear parameter in Gui::SoFCColorBar to just set it's position (I'd be happy to be proven wrong), so I'll need to dig in a bit. While this bug itself should be fixed, I don't know how much of the post-processing we would want to handle locally within FreeCAD. There are other programs that are built for exactly this purpose (looking mainly at ParaView), and I believe it'd be kind of a duplication of effort to support more complex behavior. |
|
This ticket has been migrated to GitHub as issue 6047. |
Date Modified | Username | Field | Change |
---|---|---|---|
2020-04-15 16:23 | fc_tofu | New Issue | |
2021-02-06 06:49 | abdullah | Target Version | => 0.20 |
2022-02-03 13:47 | Kunda1 | Note Added: 0016343 | |
2022-02-03 13:51 | Kunda1 | Tag Attached: #pending | |
2022-02-03 21:40 | Kunda1 | Note Added: 0016345 | |
2022-02-03 21:41 | Kunda1 | Severity | trivial => minor |
2022-02-03 21:41 | Kunda1 | Status | new => acknowledged |
2022-02-03 21:42 | Kunda1 | Tag Attached: #ready-for-migration | |
2022-02-03 21:42 | Kunda1 | Tag Detached: #pending | |
2022-02-04 19:49 | jnxd | Note Added: 0016356 |