You could also update the 'scalar' help patch, which you get when you get help on a visual instance of a data structure. It is in SVN here:
http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/doc/pddp/ scalar-help.pd .hc On Apr 22, 2008, at 5:04 PM, Luke Iannini (pd) wrote: > On an unrelated note, I just discovered: > Option/Command click on an element to duplicate the element (it's best > to click and drag since it will appear on top of the element you click > on), or just to the left of the element to delete it (when using > Option, cursors appear to let one know which operation will occur, but > oddly not with Command). > > Shift-dragging an element moves it *and* all following elements > after it. > > I was vaguely aware of Command-clicking to add elements (though I had > never gotten it to work), but I had no idea about deleting and > dragging, both of which will be extremely useful in a sequencing > context. > > I guess I'll stick these in the wiki somewhere. > > Cheers > Luke > > On Mon, Apr 21, 2008 at 11:14 AM, Luke Iannini (pd) > <[EMAIL PROTECTED]> wrote: >> Hallo, >> I'm continuing work on a data structure sequencer, and have switched >> to using arrays for performance reasons thanks to Frank and Miller's >> suggestion. That worked quite well! Thanks again. >> >> One door leads to another, of course: I've run into an odd issue >> when >> using the relatively recent grain and scale definitions with the >> elements of the array. I've attached a modified version of >> 05.array.pd to demonstrate. Dragging array elements with the mouse >> becomes erratic as soon as the "-y y(0:100)(0:1000)(1)" or similar >> instruction is added to [plot], in that very fast mouse movements >> are >> required to effect any change (i.e. move the mouse slowly enough, >> and >> the element won't move at all). >> >> As far as I can tell the bug applies to the direction being >> "grained", >> but adding grain/scale to -x broke things entirely for me (the >> drawing >> seemed to occur correctly, but I couldn't find any clickable >> hotspots). >> >> Finally, the hotspots for resizing elements also become displaced in >> the x direction. In the patch, try resizing the rightmost green >> boxes >> in the array to see what I mean. >> >> That's all. >> >> (okay, not really. Are there any plans to add the "change" pointer >> output to elements of an array? Their [struct]s remain silent.) >> >> Cheers >> Luke >> > > _______________________________________________ > PD-list@iem.at mailing list > UNSUBSCRIBE and account-management -> http://lists.puredata.info/ > listinfo/pd-list ------------------------------------------------------------------------ ---- Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies. - Amy Smith _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list