mini Audicle crashes when removing shreds
hi guys i continuously encounter crashes with the new version of mini Audicle. it happens when i try to remove a shred from the virtual machine, when the corresponding shred is already closed. (removing by clicking on the "-" sign in the vm form). steps to reproduce: 1: open the otf_01.ck from the examples and add it to the vm 2: close the shred window of otf_01.ck 3: remove the shred by clicking ont the "-" in the vm 3: peng! aargh.. this drives me crazy :-P unfortunately i encounter this error every 10 minutes cause i'm livecoding with a lot of shreds the same time. sorry to say, but i need to go back and use the older version - too risky for my health ;-) cheers /moudi
Hi Moudi, well... thats kind of an embarrassing one... We'll try and get a fix out as soon as possible for that. spencer On Apr 2, 2007, at 6:28 PM, Leuthold Dominik wrote:
hi guys
i continuously encounter crashes with the new version of mini Audicle. it happens when i try to remove a shred from the virtual machine, when the corresponding shred is already closed. (removing by clicking on the "-" sign in the vm form).
steps to reproduce: 1: open the otf_01.ck from the examples and add it to the vm 2: close the shred window of otf_01.ck 3: remove the shred by clicking ont the "-" in the vm 3: peng!
aargh.. this drives me crazy :-P unfortunately i encounter this error every 10 minutes cause i'm livecoding with a lot of shreds the same time. sorry to say, but i need to go back and use the older version - too risky for my health ;-)
cheers /moudi _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
Moudi/anyone else who was having this crash, This issue should now be fixed in the release versions for Windows and Linux on the miniAudicle website (this problem doesn't seem to affect OS X currently). Its still listed as 0.1.3.7 on the website, but in the About... dialog it should say 0.1.3.7d. Please let us know if any major problems persist. thanks, spencer On Apr 2, 2007, at 6:28 PM, Leuthold Dominik wrote:
hi guys
i continuously encounter crashes with the new version of mini Audicle. it happens when i try to remove a shred from the virtual machine, when the corresponding shred is already closed. (removing by clicking on the "-" sign in the vm form).
steps to reproduce: 1: open the otf_01.ck from the examples and add it to the vm 2: close the shred window of otf_01.ck 3: remove the shred by clicking ont the "-" in the vm 3: peng!
aargh.. this drives me crazy :-P unfortunately i encounter this error every 10 minutes cause i'm livecoding with a lot of shreds the same time. sorry to say, but i need to go back and use the older version - too risky for my health ;-)
cheers /moudi _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
wow spencer that's real JIT development :-)) bug is gone, time for a excessive livecoding session!! woohoo /moudi
-----Ursprüngliche Nachricht----- Von: chuck-users-bounces@lists.cs.princeton.edu [mailto:chuck-users-bounces@lists.cs.princeton.edu] Im Auftrag von Spencer Salazar Gesendet: Dienstag, 3. April 2007 19:17 An: ChucK Users Mailing List Betreff: Re: [chuck-users] mini Audicle crashes when removing shreds
Moudi/anyone else who was having this crash, This issue should now be fixed in the release versions for Windows and Linux on the miniAudicle website (this problem doesn't seem to affect OS X currently). Its still listed as 0.1.3.7 on the website, but in the About... dialog it should say 0.1.3.7d. Please let us know if any major problems persist.
thanks, spencer
On Apr 2, 2007, at 6:28 PM, Leuthold Dominik wrote:
hi guys
i continuously encounter crashes with the new version of mini Audicle. it happens when i try to remove a shred from the virtual machine, when the corresponding shred is already closed. (removing by clicking on the "-" sign in the vm form).
steps to reproduce: 1: open the otf_01.ck from the examples and add it to the vm 2: close the shred window of otf_01.ck 3: remove the shred by clicking ont the "-" in the vm 3: peng!
aargh.. this drives me crazy :-P unfortunately i encounter this error every 10 minutes cause i'm livecoding with a lot of shreds the same time. sorry to say, but i need to go back and use the older version - too risky for my health ;-)
cheers /moudi _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
On a related note; I've been having tourble with the "alt + +" hotkey for adding shreds (Windows). In some situations, particularly when the VM is empty, this one acts dfferently from the on-schreen button. It seems to try to replace a shred instead of plainly adding it and -of course- this makes it complain about there not being a target shred when the VM is empty. The result is a non-functional hotkey and a smasll error message. I think (but I'm not 100% sure) it doesn't do that for the first time a shred it exectured, or maybe it's simply inconsistent but I do know that for me once it starts doing this it will stick to that behaviour. Aside from that the latest Mini has been great for me and the new settings like the default dir were very welcome. Yours, Kas.
Hey Kassen, On Apr 4, 2007, at 6:25 AM, Kassen wrote:
On a related note;
I've been having tourble with the "alt + +" hotkey for adding shreds (Windows).
In some situations, particularly when the VM is empty, this one acts dfferently from the on-schreen button. It seems to try to replace a shred instead of plainly adding it and -of course- this makes it complain about there not being a target shred when the VM is empty. The result is a non-functional hotkey and a smasll error message.
Im not sure that I've encountered this particular problem before. It might be an oddity in the code that handles this particular command, as wxWidgets doesn't natively support '+' as an accelerator key. Its supposed to always be '+'. Ill take a look, but my basic tests thus far have not turned up any unexpected behavior.
I think (but I'm not 100% sure) it doesn't do that for the first time a shred it exectured, or maybe it's simply inconsistent but I do know that for me once it starts doing this it will stick to that behaviour.
Aside from that the latest Mini has been great for me and the new settings like the default dir were very welcome.
Awesome! thanks, spencer
Yours, Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
Spencer Salazar: Im not sure that I've encountered this particular problem before. That's what you have testers for then! :-) It
might be an oddity in the code that handles this particular command, as wxWidgets doesn't natively support '+' as an accelerator key. Its supposed to always be '+'. Ill take a look, but my basic tests thus far have not turned up any unexpected behavior.
This was using a test file that entered the VM, did something, then exited so something to the tune of; SinOsc s => dac; second => now; As you might imagine; code like that never gets replaced and never gets removed manually, it only gets added. It was in a situation like that that I encountered this behaviour. I'm almost positive the culprit will be in a diference between what the "add" button does and how the "alt + +" shortcut works. Hope that helps, I'll keep a eye out for this. Kas.
Update on this issue:
I blieve I may have found the cause.
My laptop has a "normal" (US-English + ms keys) keyboard while I prefer to
use a IBM Model M (that big clicky one) with a Dutch layout. Those are quite
heavy and large so; I have the little "switch keyboard layout" utility that
comes with XP for when I don't feel like hauling that brick.
Now, it turns out that somebody thought it would be a good idea to have
"left alt + shift" bound to "switch keyboard layout" in that utility. To
make matters worse; on a US keyboard you need to use shift to reach the "+"
while on the Dutch layout you need the shift to reach the "=". Hence; whould
you also need to use the alt, for example to use the Mini's hotkeys you'll
end up hitting lerft shift and alt together.... Why not use the right alt
then, one might wonder, well, on a Dutch layout the two "alts"are different
and work in different ways (givving access to a lot of character nobody uses
much.
Basically I believe this might have caused the inconsistent behaviour.
Sorry if that caused extra confusion, in retrospect it seems quite funny...
Kas.
On 4/4/07, Kassen
On a related note;
I've been having tourble with the "alt + +" hotkey for adding shreds (Windows).
In some situations, particularly when the VM is empty, this one acts dfferently from the on-schreen button. It seems to try to replace a shred instead of plainly adding it and -of course- this makes it complain about there not being a target shred when the VM is empty. The result is a non-functional hotkey and a smasll error message.
I think (but I'm not 100% sure) it doesn't do that for the first time a shred it exectured, or maybe it's simply inconsistent but I do know that for me once it starts doing this it will stick to that behaviour.
Aside from that the latest Mini has been great for me and the new settings like the default dir were very welcome.
Yours, Kas.
participants (3)
-
Kassen -
Leuthold Dominik -
Spencer Salazar