Closed j0ni closed 1 year ago
I was fixed call sc-osc:encode-message
in sc-osc:close-device
instead osc:encode-message
.
618cd6b98be6f505adc673b1869df2d3a05a4cfb
please test it.
I use osc
package in quicklisp(osc-20190521-git) and It have encode-message
. check it your osc
package.
ah! osc
package updated (osc-20221106) and It changed API.
I need more test, but cl-collider seems works well.
please update and test it!
Thanks!
Yep, that does the trick, thank you! Please close this as you see fit.
I'm not sure what the mechanism for release is with Quicklisp. FWIW, I also use Ultralisp as a QL distribution, which releases all day every day :)
Will this fix be in the next QL update?
Thanks again!
Will this fix be in the next QL update?
maybe :-) Thank you!
Hello!
Thanks for your excellent toolkit, I'm having fun with it.
I have been stepping through your examples, and discovered that I cannot call
(server-quit *s*)
without error. Here is the stack trace with some bits expanded from a sly buffer in emacs:I'm not sure where this function is defined, but it isn't in the
osc
package - I tried quickloading that. There is anencode-message
function in theosc/osc.lisp
file, but it is below a(in-package :sc-osc)
call. I might try making that change locally to test the theory that this is what you intended, but I would like your advice.Let me know if there's anything else I can provide to help.