triggerbox: potentially useful comment about the process of slot property-setting
* first the region is scanned for bpm and one-shot status * then we handle properties that should be applied from a drag&drop * then we handle the existing arrangement-style slot properties that should persist
This commit is contained in:
parent
7d34397a35
commit
4450b5be2c
@ -2205,6 +2205,7 @@ TriggerBox::set_region (uint32_t slot, boost::shared_ptr<Region> region)
|
|||||||
return;
|
return;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
/* set_region_in_worker_thread makes some guesses about whether a clip is a one-shot or looping*/
|
||||||
t->set_region_in_worker_thread (region);
|
t->set_region_in_worker_thread (region);
|
||||||
|
|
||||||
/* if we are the target of a drag&drop from another Trigger Slot, we probably want the name, color and other properties to carry over */
|
/* if we are the target of a drag&drop from another Trigger Slot, we probably want the name, color and other properties to carry over */
|
||||||
|
Loading…
Reference in New Issue
Block a user