sts.iem.at
Betreff: Re: [PD] bug with edit-mode (was Re: [PD-announce] PD 0.49-0test1
released)
I am on Mac, yes, sorry I forgot to mention that. For me the problem is
happening whenever a donecanvasdialog message is sent to a canvas, so I'd
imagine that is triggering the same thing as the prope
I am on Mac, yes, sorry I forgot to mention that. For me the problem is
happening whenever a donecanvasdialog message is sent to a canvas, so I'd
imagine that is triggering the same thing as the properties menu would?
Also, if the donecanvasdialog message happens in an abstraction, it puts
I bet this is related to the "save as" crash bug. Are you on Mac OSX?
And... am I reading this correctly that you (1) open any patch; (2) open the
"properties" dialog for the canvas; (3) hit "OK" on the dialog, and then
you find out that the patch went into edit mode?
(And that it then crashes
Okay I can can confirm that using donecanvasdialog is triggering the edit
mode thing, though I'm not sure why there is no indication from pd upon
loading a patch on startup that it is, in fact, in edit mode. I tried some
patches made by other people, such as waveform.mmb or whatever it is
called,
Well I know that the canvas is in edit mode as anytime I try to click
anything I end up grabbing something and resizing it instead, and toggling
edit mode on and off in the edit menu makes it behave as expected. The
thing with having no indication of currently being in edit mode was only
happening
hi.
thanks for the bug-report.
unfortunately it indeed doesn't contain much information about what
could be the actual problem you are experiencing.
things i could establish:
- your patches switch to edit-mode when they shouldn't
- there is no indication of being in edit-mode
- you accidentally
