View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000331 | ardour | bugs | public | 2004-03-16 18:52 | 2008-11-21 00:00 |
| Reporter | rlm | Assigned To | cth103 | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000331: segment layer order change. | ||||
| Description | When puhsing a sgement to back layer, moving the segment place it again on the top. The layer number should remain the same when a "non on top" segment is moved. | ||||
| Additional Information | ardour: CTK 0.453.1 libardour 0.728.1 jack 0.2.5 / build Keb 16 2004 / jackd 0.94.0 Redhat 9 / Gnome kernel: alsa-kernel-2.4.24-1.ll.rh90.ccrma processor: AMD Atlon 850MHz main board: DFI AK74-EC disk: HD1 = 40GO / HD2 = 120 GO | ||||
| Tags | No tags attached. | ||||
|
|
the problem with your request (which seems entirely reasonable on the surface) is this: if you drag a region that is (for example) on the bottom layer, then while dragging it will remain visible (so you can see what you are doing). but if you dragged it on top of another region, then when you end the drag, it will "sink" below the upper region and will be invisible. this is very counter-intuitive behaviour. on the other hand, if there is no overlap when the drag ends, then yes, its hard to see why the layering should change. |
|
|
Thank you Paul for this answer. IMHO, the layer-number feature is useless if, as soon as you touch a segment, it is reset on the top. One must keep in mind that the other extremity of the last segment you touched is also now on top, then must go back to the other end, and check if this is acceptable or not, re-adjust it if not, then check the next/previous end, etc. I imagine if you carefully set vertical segment ordering (kind of "tiling"), you do not want it jeopardized by just trimming a mount point somewhere. If you can select a non-on-top segment to move it, this obviously means you're able to see it. I think that there are few chances for such segment to require a large time shift, and that the risk of having it suddenly hidden is low. May I suggest to never change the segment layer order, but to set segments "transparent" by default, or set to transparent a segment that may hide another one after a shift. |
|
|
Is this still an issue? |
|
|
Marking as resolved; there are new options to control layering now, and the original reporter has not replied for a while. Feel free to leave a comment if there are still problems! |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-03-16 18:52 | rlm | New Issue | |
| 2004-04-12 12:41 | paul | Note Added: 0000616 | |
| 2004-04-14 18:09 | rlm | Note Added: 0000630 | |
| 2007-02-14 21:38 | taybin | Note Added: 0003247 | |
| 2007-05-17 11:21 | cth103 | Status | new => resolved |
| 2007-05-17 11:21 | cth103 | Resolution | open => fixed |
| 2007-05-17 11:21 | cth103 | Assigned To | => cth103 |
| 2007-05-17 11:21 | cth103 | Note Added: 0003988 | |
| 2008-11-21 00:00 | seablade | Status | resolved => closed |
