4.6.1 Collection Issue

Archive of the non-categorized posts related to the QLC+ technical support.
Please do not create new threads here, instead, use the categories above !
Post Reply
George Qualley

I just wanted to mention that I noticed an issue with collections under 4.6.1. After making a new collection or duplicating a collection, I cannot add anything to that collection because the "OK" button in the Select Function dialog remains inactive.
Massimo Callegari

Hi George, this sounds like a bad thing :(
Have you checked this happens only on Collections ?
Cause it should behave the same everywhere now.
George Qualley

Hi Massimo,

I checked just now and it definitely happens with the collections even in a brand new project. The only other area where I can think of a similar dialog right now is when adding things to a chaser and it doesn't appear to happen there.
Massimo Callegari

Weird...and scary o__O
Jano Svitok

Hi all,

it seems that if you uncheck collections in the function selection dialog, and then select a function, OK button is enabled again.
Massimo Callegari

Are we sure this wasn't there before ?
Can anyone try with 4.6.0, cause I haven't touched that part of the code...
Ulf

Massimo,


I can confirm that under Ubuntu 13.10, x86_64, version 4.6.0 is OK but 4.6.1 shows the behaviour George mentioned. The OK Button remains inactive.
Hope that helps,

best regards,
Ulf
Joe

I am having this issue trying to add scenes to a chaser..

This is a new project.
Attachments
Joe%27s%20uMBP%20at%202014-01-15%20at%2020.31.02.png
Joe%27s%20uMBP%20at%202014-01-15%20at%2020.31.02.png (68.58 KiB) Viewed 640 times
Jano Svitok

Workaround: Sometimes it helps to toggle some of the checkboxes. For Joe, switch chasers off, for George, switch collections off.
CShark

Another thing to be mentioned: If you create 2 collections directly after another, and then select the first one, the ok button is enabled. If you select the second one, the button is disabled.

If you delete the last one before editing the one before, the one before will become disabled instead.

A workaround seems to be: Create n+1 collections/chaser, configure them and then remove the last one.
Post Reply