[Csnd] QuteCsound Display Widget Question

[Csnd] QuteCsound Display Widget Question

Date	2011-08-23 22:03
From	Jim Aikin
Subject	[Csnd] QuteCsound Display Widget Question
	Here's a dumb question -- I'm sure there's a simple answer, but I can't figure it out. I'm running the Display_Widget.csd example in QuteCsound 0.6. (By the way, there's a bug in this example ... the line [ktempo invalue "tempo"] needs to be added to instr 1.) When I run the example, the values in two display widgets are updated. This is done using the outvalue opcode. But I'll be damned if I can see where the channel names of these two widgets ("time" and "location") are encoded. They sure as heck aren't visible in the Properties boxes for the two widgets. So where are the channel names hiding? Thanks. --Jim Aikin -- View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-Display-Widget-Question-tp4728265p4728265.html Sent from the Csound - General mailing list archive at Nabble.com. Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2011-08-23 23:39
From	Rene Jopi
Subject	Re: [Csnd] QuteCsound Display Widget Question
	Hi, These widgets should be display widget !! In my example , they are label widget. If i am not wrong, this example were created during the time of label widget having a channel name. Now, label widget don't have a channel name in its windows properties but it is still alive in the text file for "old" csd (can see with a text editor). Am I correct? René 2011/8/23 Jim Aikin <midiguru23@sbcglobal.net> Here's a dumb question -- I'm sure there's a simple answer, but I can't figure it out. I'm running the Display_Widget.csd example in QuteCsound 0.6. (By the way, there's a bug in this example ... the line [ktempo invalue "tempo"] needs to be added to instr 1.) When I run the example, the values in two display widgets are updated. This is done using the outvalue opcode. But I'll be damned if I can see where the channel names of these two widgets ("time" and "location") are encoded. They sure as heck aren't visible in the Properties boxes for the two widgets. So where are the channel names hiding? Thanks. --Jim Aikin -- View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-Display-Widget-Question-tp4728265p4728265.html Sent from the Csound - General mailing list archive at Nabble.com. Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2011-08-24 05:03
From	Jim Aikin
Subject	[Csnd] Re: QuteCsound Display Widget Question
	Thanks, René. That explains it. But it raises a larger question: Are the Widget examples (or other examples) being scrutinized and possibly revised for the next release of QuteCsound? And do we know yet when that release will happen? The reason I'm asking is because I'm working on a book that will include a whole chapter on the details of how to work with QuteCsound. If there are points of confusion like this in the examples, I need to document them ... but it would be a waste of time for me to document them if they're going to disappear before the book is published. I seem to recall that a release date of July 15 was being mentioned at one time. Possibly it's the lack of a Windows compile that's delaying the release. I tried to do that, but I got into a weird hangup that Andres was not immediately able to diagnose, and I haven't heard anything from him for a couple of weeks. Admittedly, I was well out of my depth, but I was hoping to be able to help.... --JA -- View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-Display-Widget-Question-tp4728265p4729175.html Sent from the Csound - General mailing list archive at Nabble.com. Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2011-08-26 11:03
From	mantaraya36@gmail.com
Subject	Re: [Csnd] Re: QuteCsound Display Widget Question
	Hi Jim, QuteCsound is now so large that it's people like you who do the scrutinizing. I will make a note of this problem to fix before the next release, which has been promised for months now... I got an old laptop this week which I'll install windows on, so hopefully I can finish sorting out the release issues for the upcoming alpha release. hopefully I will sort out your problem so you can start running development versions to help make sure windows bugs are properly addressed. Actually the best way you can help is just deleting the label and creating a display widget in its place. If you send me the corrected file I can quickly add it to svn. The current state is that the actual program should be working ok, but there needs to be some work on the installers for all platforms since the McCurdy collection which is now included needs to be packaged differently to the rest of the examples (they will actually be files on the hard drive rather than files embedded in the binary). I will try to make a new release before Sept. 15, now that I've finished one major commitment. Cheers, AndresOn Wed Aug 24 05:03:29 2011 Jim Aikin wrote: Thanks, René. That explains it. But it raises a larger question: Are the Widget examples (or other examples) being scrutinized and possibly revised for the next release of QuteCsound? And do we know yet when that release will happen? The reason I'm asking is because I'm working on a book that will include a whole chapter on the details of how to work with QuteCsound. If there are points of confusion like this in the examples, I need to document them ... but it would be a waste of time for me to document them if they're going to disappear before the book is published. I seem to recall that a release date of July 15 was being mentioned at one time. Possibly it's the lack of a Windows compile that's delaying the release. I tried to do that, but I got into a weird hangup that Andres was not immediately able to diagnose, and I haven't heard anything from him for a couple of weeks. Admittedly, I was well out of my depth, but I was hoping to be able to help.... --JA -- View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-Display-Widget-Question-tp4728265p4729175.html Sent from the Csound - General mailing list archive at Nabble.com. Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2011-08-26 11:08
From	mantaraya36@gmail.com
Subject	Re: [Csnd] QuteCsound Display Widget Question
	Hi Rene, This is exactly the case. They should be display widgets. You can delete them and recreate them or you could edit the xml itself on another editor to change the widget type. The reason for this change had to do with presets. If I had left a channel for labels, I would've had to store the contents of ALL the labels for each preset, which would be a big waste of space, so I removed that option. Labels should be "static" anyway. I just forgot to update the display examples which for some reason relied on the old behavior. Cheers, Andres On Tue Aug 23 23:39:56 2011 Rene Jopi wrote: Hi, These widgets should be display widget !! In my example , they are label widget. If i am not wrong, this example were created during the time of label widget having a channel name. Now, label widget don't have a channel name in its windows properties but it is still alive in the text file for "old" csd (can see with a text editor). Am I correct? René 2011/8/23 Jim Aikin <midiguru23@sbcglobal.net> Here's a dumb question -- I'm sure there's a simple answer, but I can't figure it out. I'm running the Display_Widget.csd example in QuteCsound 0.6. (By the way, there's a bug in this example ... the line [ktempo invalue "tempo"] needs to be added to instr 1.) When I run the example, the values in two display widgets are updated. This is done using the outvalue opcode. But I'll be damned if I can see where the channel names of these two widgets ("time" and "location") are encoded. They sure as heck aren't visible in the Properties boxes for the two widgets. So where are the channel names hiding? Thanks. --Jim Aikin -- View this message in context: http://csound.1045644.n5.nabble.com/QuteCsound-Display-Widget-Question-tp4728265p4728265.html Sent from the Csound - General mailing list archive at Nabble.com. Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2011-08-27 22:14
From	Jim Aikin
Subject	[Csnd] Re: QuteCsound Display Widget Question
	On 8/26/2011 3:38 AM, Andres Cabrera [via Csound] wrote: > Hi Jim, > > QuteCsound is now so large that it's people like you who do the > scrutinizing. I will make a note of this problem to fix before the > next release, which has been promised for months now... I got an old > laptop this week which I'll install windows on, so hopefully I can > finish sorting out the release issues for the upcoming alpha release. > hopefully I will sort out your problem so you can start running > development versions to help make sure windows bugs are properly > addressed. That would be great. I'm happy to help. > Actually the best way you can help is just deleting the label and > creating a display widget in its place. If you send me the corrected > file I can quickly add it to svn. See Display_Widget_New.csd, attached. I've replaced all three of the active Label widgets with identical Display widgets. Also, I've attached a test file that you might want to look at. The Button widget's Properties box lets me set a value, which I would suppose is intended to be its output when clicked. I've given four buttons all the same channel name, but different output values, with the idea that I could send different values to that channel by clicking different buttons. But that doesn't work. No matter which button I click, I get an output of the value set in the FIRST button created for that channel. Of course, there are other ways to code this that would work -- give each button a different channel name, and then let Csound keep track of which channel has sent a message most recently. But it would be nice if the button widget's own code could handle a situation where several buttons are transmitting on the same channel, with different values. It would also be nice, as a suggestion, to allow buttons to operate in either momentary or toggle mode. In that case, they would need a different graphic appearance for 'on' than for 'off', so that might be more complexity than you want to deal with right now. > The current state is that the actual program should be working ok, but > there needs to be some work on the installers for all platforms since > the McCurdy collection which is now included needs to be packaged > differently to the rest of the examples (they will actually be files > on the hard drive rather than files embedded in the binary). > I will try to make a new release before Sept. 15, now that I've > finished one major commitment. I'm sure you're very busy. I think what I'll do is work on the rest of my book and leave the work on the QuteCsound chapter for last. --JA Display_Widget_New.csd (11K) Download Attachment MultiButton_Widget.csd (8K) Download Attachment View this message in context: Re: QuteCsound Display Widget Question Sent from the Csound - General mailing list archive at Nabble.com.

Date	2011-08-29 21:32
From	Andres Cabrera
Subject	Re: [Csnd] Re: QuteCsound Display Widget Question
Attachments	button_test.csd
	Hi Jim, On Sat, Aug 27, 2011 at 10:14 PM, Jim Aikin <midiguru23@sbcglobal.net> wrote: See Display_Widget_New.csd, attached. I've replaced all three of the active Label widgets with identical Display widgets. Can you resend the attachments? They're not working for me... Also, I've attached a test file that you might want to look at. The Button widget's Properties box lets me set a value, which I would suppose is intended to be its output when clicked. I've given four buttons all the same channel name, but different output values, with the idea that I could send different values to that channel by clicking different buttons. But that doesn't work. No matter which button I click, I get an output of the value set in the FIRST button created for that channel. Of course, there are other ways to code this that would work -- give each button a different channel name, and then let Csound keep track of which channel has sent a message most recently. But it would be nice if the button widget's own code could handle a situation where several buttons are transmitting on the same channel, with different values. That is currently working for me. I can't remember if there was any change in this respect, but it's working fine on my sources. Are you sure you've set the buttons to be of value type? Can you try the attached file to see if it doesn't work on the released version? It would also be nice, as a suggestion, to allow buttons to operate in either momentary or toggle mode. In that case, they would need a different graphic appearance for 'on' than for 'off', so that might be more complexity than you want to deal with right now. That is actually also implemented already in the dev version... I really need to get all this out. I'm sure you're very busy. I think what I'll do is work on the rest of my book and leave the work on the QuteCsound chapter for last. Thanks! I will try to get a release out before the 15th. Cheers, Andres