ability to disable right click in ... - mIRC Discussion Forums

I want the ability to disable the right click menu in custom/picture windows as it gets annoying, or just have the other menu items hidden so the ones told to show for that window are the only ones seen

What "other menu items" are you talking about? Custom/picture windows only display items that you specify in a menu definition. If you have other scripts that do
menu * {

}
or similar, thus adding items to all windows, including custom ones, you should fix those by making them less general.

Personally, I'd also like to have some way when creating custom windows that prevents menu items not specific to that custom window from being there as well. This would allow your custom window to only have specific menu items when someone else uses it even if they have other scripts that insert menu items all over the place instead of specific.

This could be a switch in the /window command or else a menthod in menu { } to prevent other menu items from showing...

Code:

menu @mycustomwindow {
  haltdef
  OnlyMyMenu
  .AndMySubmenu:Do this
}

It's fine to make your own menus more specific, but if you want to distribute your script(s), you can't control what other scripts users use.

Maybe a switch to keep ordinary * menus from appearing in your custom window.

Code:


menu -r @mywindow {
  OnlyMyMenus:cmd
}

And maybe another switch to make menus ignore the -r setting?

Code:


menu -R @mywindow {
  ALLWindows:cmd
}

-genius_at_work

Yep, those would work.

that would be nice, but woudlnt it screw up backwards compadability?

No, because "-r" isn't a valid menu parameter anyway, so there's no syntactic conflict.

Right, it wouldn't cause problems because the -r wasn't present previously. Of course, older scripts that *want* you to display their menu in every window even if it's some other script's custom window won't be able to... but who really cares? There's no reason why they should in the first place.

It would be taking control away from the user who should be able to add a menu to whatever custom window they want.

Right. But the problem is the occasional mis-use of menu * { } - taking control away from your own addon/script by enforcing a "third party" popup. Folks *should* use menu <definition> { } propperly, but at times they don't.
Consciously enforcing a menu by -R differs from "accidentally" using the catch-all * menu definition.
Btw: "halt" takes control over events away from you by now - starting the infamous struggle for file order.

Misuse or not, user control trumps script control, as it should be.

~ Edit ~
I believe there was a similar argument some time ago about adding a timer switch to stop a timer from being halted by using /timers off.