I'm working with an AREV 3.12 application. I was resently been discovered that a user can hit the F10 button while in a popup and bring up the APPMAIN menu. Any user can do this. So far I haven't found any way to set a key disable on popups like you can on windows. Can anyone point me in the right direction on what keys are available to a popup and how to disable one or more of them? For something like an F10, it's something we'd probably want to disable on all popups. Where other keys we may want to selectively disable or enable depending on some set of conditions.

I do know about the CTRL-F9 key combination that displays the Active Key List for Popups, Windows and other things.

Thank you for your time.

Michael Slack

Michael,

I can think of two things. First, under the environment settings, there is a "default menu" option. I can't remember exactly where it is, however. This is most likely set to "APPMAIN". If you change this to your application main menu, that should fix this issue.

The other option is to write your own wrapper to call pop-ups. This wrapper can remove any unwanted keystrokes from @PRIORITY.INT and other keystroke arrays, call the popup, and then restore the arrays.

This would allow you to temporarily disable those keystrokes in a popup. However, I think the issue is really with the default menu definition under the environment settings.

msorrel@greyhound.com

Greyhound Lines, Inc.

Thanks Matt. I think I'm going to try your first option. In my looking around, I've come accross where APPMAIN is set as the default menu. I'm going to have to run it by a few folks here to make sure it doesn't blow someone out of the water in some way. I doubt it but you never now.

Again, thanks,

Michael Slack

Michael,

If there are some people that need that, you can give them custom configurations with that as their default menu, and then have your "standard" environment settings as your application main menu.

msorrel@greyhound.com

Greyhound Lines, Inc.

Hello Matt:

I'll keep that in mind but the people who will need APPMAIN are computer savey enough to use the RUNMENU command.  Plus the way we have our systems configured with internal security levels, the people who'll need and should have access to APPMAIN also have access to the RUNMENU command.  Our main concern is to keep such a powerful set of tools out of the hands of the average user.  In the last couple of months we've had a few intances where a user stumbled into APPMAIN and  wandered around and did a few things.  Fortunately, they didn't do any real damage but it's a large security whole for us and were trying to fix it.  I'm trying to craft a fix that will only let the authorized users get to that menu and keep everyone else out but do in a way that is as seamless as possible.  Your first suggestion seems to be the way to go at first glance.  Your second suggestion sounds like it might be a bit of work and I'd need to be very careful just because of the way some of our stuff does things.  It's good to have an alternate plan in case the first doesn't work out.

Thanks,

Mike

View this thread on the forum...