Page 1 of 1

Posted: 25 Feb 2010, 11:33
by kara
Is a listbow slower then other controls ?


Example the follwing patch
Image

I would expect that the 'Chord' textfield is updates as the 'Bar counter' textfield, but there is big latency between the two...
Normal ?

A solution to syncronise both ?

k

Posted: 25 Feb 2010, 12:14
by nay-seven
the + module is a " + 1 "...?

Posted: 25 Feb 2010, 13:10
by kara
Yes it is +1 module, but it is the listbox that is slower....

k

Posted: 25 Feb 2010, 13:27
by nay-seven
i ask this because , the first data of a module in Usine is always the 0, so the first data in your listbox correspond to 0..
so maybe a problem of difference here..?

Posted: 25 Feb 2010, 14:43
by kara
thanks for your idea nay-seven,
I've changed it to show the next upcomming chord, which is actually more logic

k

Posted: 25 Feb 2010, 20:17
by gurulogic
I've noticed the listboxes to be a bit slow in the past, but slow as in perhaps a couple of milliseconds, not anything you should be able to viually identify...

Posted: 25 Feb 2010, 20:24
by 23fx23
I wonder if it's related or not, but as i went back in my big sq patch, cpu was going crasy,
it took me a while to identify where the pb came from
and i discovered it was coming from a list box that drive it's text to a sendbus name.
the patch was ok with v4, so i supposed it wasn't a bus conflict,

i repatched with no bus but nedded then lot of wires, works ok with the wire equivalent but can be boring...
very strange...

Posted: 25 Feb 2010, 21:46
by gurulogic
I should mention I noticed the slow listboxes in v4..2 I haven't bothered seeing if they are changed in v5 so maybe there could be a problem?

23fx23,
if you can recreate it, maybe you should run that one by Senso? The buses are quite rebuilt in v5 and it took a few bug reports to get them all working properly for me.

Posted: 25 Feb 2010, 23:56
by 23fx23
yes i have to investigate a bit more when free time and report to senso......was not "logical"but i have to debug and make few tests to confirm...