DMX channel monitor size not loaded properly

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
siegmund
Posts: 703
Joined: Mon Nov 02, 2015 11:03 am
Location: Germany
Real Name: Lukas

Hey guys,

while playing around I picked up another issue:

When loading a workbench, the size of the DMX channel monitor is displayed as saved in the workbench, but not properly represented by numbers in the "size" textfields. Instead of showing the new values, the size of the last opened project is displayed.
It's not such a great bug, but a bit annoying when switching through projects for testing some things.

I'm runnig QLC+ 4.10.1 on Ubuntu 14.04.

See attached some files for reproducing (ignore fixtures/functions/etc and try it with DMX channel monitor enabled and in the foreground).


7 minutes are running :D ;)
plugz
Posts: 637
Joined: Sun Apr 12, 2015 6:30 pm
Real Name: David

Yes, you're right. Thanks.

https://github.com/mcallegari/qlcplus/issues/669


EDIT- I won't do this one under 7 minutes :p
siegmund
Posts: 703
Joined: Mon Nov 02, 2015 11:03 am
Location: Germany
Real Name: Lukas

Thank you for opening the issue - am I allowed to open issues directly on github without posting in the forum?

You would have seen me really surprised if someone did this again :D
plugz
Posts: 637
Joined: Sun Apr 12, 2015 6:30 pm
Real Name: David

Yes you can open issues on github directly :) it easier to track afterwards.
User avatar
mcallegari
Posts: 4827
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

I prefer issues to be reported here first.
If they are confirmed, then an issue can be opened on GitHub.

I'd like to have GitHub used only by developers, otherwise the issues there will start get messy and moreover we'd have a bunch of false positive and a number of colorful requests.
siegmund
Posts: 703
Joined: Mon Nov 02, 2015 11:03 am
Location: Germany
Real Name: Lukas

Sorry I read this too late - already opened an issue on github for another thing.

I definitely see your point (that's why I asked).

Feel free to close/delete issue #670 on github, then I will post it here first.
Sorry!
Post Reply