Re: [PD] avoid "properities"/"open" options in abstractions

On 2018-04-20 05:52, Alexandre Torres Porres wrote: > well, I'm now confused, cause it was mentioned how Gem automatically adds a > path to Pd to load abstractions, so I was testing that even though I never > used Gem, and I was checking its abstractions, like gemmouse, to see if it > was

Re: [PD] avoid "properities"/"open" options in abstractions

well, I'm now confused, cause it was mentioned how Gem automatically adds a path to Pd to load abstractions, so I was testing that even though I never used Gem, and I was checking its abstractions, like gemmouse, to see if it was instantiated without the path added. It got created, but I couldn't

Re: [PD] avoid "properities"/"open" options in abstractions

Hi, I just learned that the Gem library similarly achieves what I wanted somehow... If you don't have the Gem library in the startup, you can load an abstraction like gemmouse and click it to open or right click it and get all the options (properties, open, help). But when the library is loaded,

Re: [PD] avoid "properities"/"open" options in abstractions

Yeah, I was like "does this object really exist?" :) But then, this is not what I was looking for. I can see it doesn't allow you to open the subpatch, but it still shows the "open" option in the menu when you right click it. I know there can be different strategies to achieve practically

Re: [PD] avoid "properities"/"open" options in abstractions

d-l...@mail.iem.at" <pd-l...@mail.iem.at> > Betreff: Re: [PD] avoid "properities"/"open" options in abstractions > > IOhannes m zmölnig wrote: > > On 04/12/2018 10:44 PM, Alexandre Torres Porres wrote: > >> But how to overwrite i

Re: [PD] avoid "properities"/"open" options in abstractions

IOhannes m zmölnig wrote: On 04/12/2018 10:44 PM, Alexandre Torres Porres wrote: But how to overwrite it only when I'm dealing with a particular canvas? I can't find the answer to this by checking propertybang, and I'm not even sure it can be done in any way. why would you want to do that on

Re: [PD] avoid "properities"/"open" options in abstractions

Hi, thanks, yeah, I had checked properties before like you suggested earlier. And I see how it has extra code to not make the new properties behaviour affect all canvases. I think I'm ok with that. But I can just use that same logic and put the *tcl* code instead. I have other issues when trying

Re: [PD] avoid "properities"/"open" options in abstractions

On 2018-04-12 04:02, Alexandre Torres Porres wrote: > subpatch or abstraction. But well, can it even be possible to tweak with > this without affecting all of Pd? > > Any ideas? take a look at how this is handled in iemguts' [propertybang]. mgfasdrt IOhannes signature.asc Description:

Re: [PD] avoid "properities"/"open" options in abstractions

Hi, today I got back to giving this a chance. I see tcl/pdtk_canvas.tcl has the *proc ::pdtk_canvas::pdtk_canvas_popup* function that deals with this. I was able to make an external that

Re: [PD] avoid "properities"/"open" options in abstractions

2018-03-06 16:02 GMT-03:00 Alexandre Torres Porres : > I have a couple of such examples in my library. > Actually I have much more, dozens of it, as I don't think any non graphical abstraction of mine needs properties! I was just thinking and meant about the graphical ones,

Re: [PD] avoid "properities"/"open" options in abstractions

yes, I know, and it's great and awesome, but there might also be the case where you don't really want to have any properties at all, cause it's just a simple abstraction. I have a couple of such examples in my library. And I think it would be worse to come up with dummy properties just for the

Re: [PD] avoid "properities"/"open" options in abstractions

On 03/06/2018 07:23 PM, Alexandre Torres Porres wrote: > Now, in my defense, I can say there could be not so pointless features > here. Like, I have a nice GUI abstraction, and people may think it's an > external and that they can change its properties, but it's not, so it'd be > nice to suppress

Re: [PD] avoid "properities"/"open" options in abstractions

Yeah, like I said, I can see the criticism, but I was hoping to avoid the discussion and just stick to the technical issue if it is possible or not. Now, in my defense, I can say there could be not so pointless features here. Like, I have a nice GUI abstraction, and people may think it's an

Re: [PD] avoid "properities"/"open" options in abstractions

On 03/06/2018 06:29 PM, Alexandre Torres Porres wrote: > Nope, the idea is just try and make an abstraction behave like a compiled > external. I know some people might think that's crazy, ludicrous, > pointless, stupid, counterproductive, shameful and just bad... but... I > liked the idea :) it

Re: [PD] avoid "properities"/"open" options in abstractions

2018-03-06 6:34 GMT-03:00 IOhannes m zmoelnig : > On 2018-03-06 00:53, Alexandre Torres Porres wrote: > > the right-click menu can be changed Ok, but how about being suppressed? Can it be? > (e.g. see the iemguts' [propertybang] object, which changes the effect of > the

Re: [PD] avoid "properities"/"open" options in abstractions

On 2018-03-06 00:53, Alexandre Torres Porres wrote: > Hi, I'm looking for a way to avoid "properties" from popping up as an > option when right clicking in an abstraction. > > This is not really "important", basically only merely aesthetical, as I > want to make abstractions look more closely as