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 compiled objects... but anyway, please don't judge :)
So, is there a way to do it? Like an external out there? If not, I guess I need to figure out how to make my own...
Moreover, I'm also after a way to avoid clicking on an abstraction and opening it, or also even preventing the "open" option from the right click menu as well.
Thanks
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 compiled objects... but anyway, please don't judge :)
So, is there a way to do it? Like an external out there? If not, I guess I need to figure out how to make my own...
Moreover, I'm also after a way to avoid clicking on an abstraction and opening it, or also even preventing the "open" option from the right click menu as well.
the right-click menu can be changed, but this would apply to *all* abstractions, not just specific ones (e.g. see the iemguts' [propertybang] object, which changes the effect of the "Properties" item in the menu, and requires some extra code to hide this for canvases that don't have a a [propertybang] object).
but if you just want to prevent users from opening up objects in your publicly facing installation, i'd do:
anything, this will prevent the abstraction from being opened by "just clicking")
(HidePopup True), so the abstractions cannot be opened via the context-menu either.
fgmasdr IOhannes
2018-03-06 6:34 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:
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 "Properties" item in the menu, and requires some extra code to hide this for canvases that don't have a a [propertybang] object).
Awesome!!! And I guess one can use this and then don't do anything with the bang output, this would effectively avoid the canvas properties from showing up, but my ideal concept would be completely hide and avoid the "properties" option to be highlighted and show up.
I wonder if it is possible at all... [propertybang] shows us how to change and mess with it, but how would you actually hide the properties?
but if you just want to prevent users from opening up objects in your publicly facing installation
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 :)
Thanks!
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 *is* pointless.
apart from that, the iemlib (iemlib2 to be precise) has an (equally pointless) object called [protect_against_open] which will just close the canvas whenever you try to open it.
gfrdsa IOhannes