[PD] A strange question (yet again)

[João Pais]

some ideas:

- try to reduce the quantity of elements so that it's manageable, but 
this isn't that well as it reduces the quality as well
- a extra problem with this is that if you want to add arrays such as 
with multiarray, you'll need to do all that in a gop - and that adds 
processing weight, making everything even heavier

- you could use GEM to display all these elements and keep the quality. 
I didn't understood if the red lines have user interaction; if yes, I'm 
not sure if one can grab "objects" in gem, probably not. but by seeing 
the mouse values it would be easy to connect the interaction with a 
definite array. Disadvantage is that gem has to be downloaded and 
installed (or you pack it with your externals)

> Indeed I think that I will have to do an external… I wonder if there is a good (simple) how-to on GUI external for Pd that are cross platform and canvas compatible… the IEM link is dead and the example code you propose is long (i.e. 1k lines long :) - I only need to take in lists and draw a coloured point in a given coordinate after all :)
>
> Then I can relearn TCLTK which I had to learn 25 years ago when working on v1 of Cecilia :)
>
>
>
>> On 21 Jan 2022, at 14:33, Christof Ressi <info at christofressi.com> wrote:
>>
>> Unfortunately, Pd's GUI capabilities are rather limited. There's probably no way around writing your own Tcl/Tk code.
>>
>> Here's an advanced example from the "else" library: https://github.com/porres/pd-else/blob/master/Classes/Source/keyboard.c.
>>
>> Generally, it would be better to add a GUI plugin, but there are some obstacles (see https://github.com/pure-data/pure-data/issues/1555)
>>
>> Christof
>>
>> On 21.01.2022 10:59, Pierre Alexandre Tremblay wrote:
>>> Ok lovely people. I cleaned it, and I even did a similar thing to João’s 'dynamic patching' to see if it would be faster. In my case, it is unusably slow for 300x400 for the struct version, and it beachballs completely with the ‘dynamic patching’ approach.
>>>
>>> Even more funny is, if you save the patch once it is drawn, the file is now huge and cannot load ;)
>>>
>>> I’ve included both patches for 30x40 for fun. At that size they both work relatively well. Now, change the numbers to 300 and 400 for less fun :) Any pointers to optimisation and/or other ideas welcome
>>>
>>> p