View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003298ardourbugspublic2010-07-01 00:362011-03-04 16:05
Assigned To 
PlatformOSOS Version
Product Version 
Target Version3.XFixed in Version 
Summary0003298: Automatic range selection in object mode
DescriptionWhen in the combined object/range mode is selected, clicking on a region in the lower half of the region (i.e. in object mode) automatically creates a range on the whole region. This should not be happening since should be in object mode.
TagsNo tags attached.
Attached Filespatch file icon auto-range-creating-on-selection-fix.patch [^] (5,057 bytes) 2010-11-06 08:49 [Show Content]

- Relationships

-  Notes
cth103 (administrator)
2010-07-04 16:48
edited on: 2010-07-04 17:32

Will have to check with the PT gang on whether this was intended.

lincoln (reporter)
2010-07-04 17:12

I have a simple fix for this but putting a patch out is difficult since there are pending patches for region transient stuff still to be applied.

If it is intended then PT is weird and they should fix this too :-)
paul (administrator)
2010-11-05 06:46

lincoln - i believe your region transient stuff is now in svn. can we see your patch?
cth103 (administrator)
2010-11-06 09:30

I'm reasonably sure that there's a reason for this behaviour, but a PT person would have to confirm.
paul (administrator)
2011-02-09 07:04

this is intended behaviour, and seems entirely logical to me. i don't really see what the issue is ...
lincoln (reporter)
2011-02-12 16:48

The behaviour seems to have changed slightly. Clicking in the lower half are range covering the region appears momentarily. If you move the region, the range becomes active at the end of the drag.

All this seem very wrong and unexpected to me. If I am in a non range mode then why should ranges be appearing when doing object mode work? Also since the automatic range is spanning the region exactly, what practical use does it have?
paul (administrator)
2011-02-13 06:11

You began this bug report with the phrase "When in the combined object/range mode is selected ..."

That's precisely the explanation of this behaviour. You are *not* in "non-range" mode, you're in a combined object/range mode in which the upper and lower half of the region have different semantics for mouse operations. This is a very powerful editing mode that a lot of PT "power users" complained that Ardour/Mixbus did not have.
cth103 (administrator)
2011-03-04 16:05

Carrying this discussion onwards post 3.0 ...

- Issue History
Date Modified Username Field Change
2010-07-01 00:36 lincoln New Issue
2010-07-04 16:48 cth103 cost => 0.00
2010-07-04 16:48 cth103 Note Added: 0008388
2010-07-04 16:48 cth103 Target Version => 3.0-beta1
2010-07-04 17:12 lincoln Note Added: 0008389
2010-07-04 17:32 cth103 Note Edited: 0008388
2010-07-05 13:13 paul Note Added: 0008399
2010-07-06 14:50 paul Note Deleted: 0008399
2010-11-05 06:46 paul Note Added: 0009357
2010-11-06 08:49 lincoln File Added: auto-range-creating-on-selection-fix.patch
2010-11-06 09:30 cth103 Note Added: 0009368
2011-02-09 07:04 paul Note Added: 0010064
2011-02-12 11:59 paul Status new => feedback
2011-02-12 16:48 lincoln Note Added: 0010080
2011-02-13 06:11 paul Note Added: 0010082
2011-03-04 16:05 cth103 Note Added: 0010284
2011-03-04 16:05 cth103 Target Version 3.0-beta1 => 3.X

Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker