|
The output is krate variables, but you need to set, not get, the values for i
time & give that value to the widget.
Probably ditto the tkinter question. You need to store your values to supply
at itime to initialise both the GUI element & any associated / linked
control rate messages i would assume.
at least that's how i've gone about it, which has only been on 1 or 2
previous occasions.
not an expert, but at least im near your time zone...
There is a way to store presets for the fltk interfaces, but i've always
thought it was as quick & easy to read & write the values to ftables
Brian Babiak wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have had fun playing with the FL opcodes lately. One question, while
> the output seems to be global k-rate variables, is there any way to get
> i rate variables, like for an ADSR envelope? Also, is there a way to
> use Tkinter or other GUI in the python opcodes and use those values?
> Thanks for the help!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFILiGEsnlT+YwreUoRAtscAJ9+/GS0lWfrN+YD6NVlmAt/xAMp5wCdG1Ud
> hSn+WsHoiYhOTGgA9Xt/Kjk=
> =OW4k
> -----END PGP SIGNATURE-----
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
-----
*******************
www.phasetransitions.net
hermetic music * python * csound * possibly mindless ranting
various werk in perpetual delusions of progress....
--
View this message in context: http://www.nabble.com/i-rate-with-fl-opcodes--tp17286428p17287564.html
Sent from the Csound - General mailing list archive at Nabble.com.
|