| Mapping Functional Keys in Forms 6i [message #84973] |
Sun, 16 May 2004 20:54  |
Rahul Desai
Messages: 26
Registered: March 2002
|
Junior Member |
|
|
Hi All,
How do you map functional keys in forms 6i. For instance, if i press key F3 then it should print the screen.
I found out that, FMRPCWEB.RES or FMRWEB.RES files has to be modified as required in order to use keys as hotkeys in an application. But i couldnot find these files at my end should i search in the server?
Im using forms 6i in windows 2000 machine.
I found fmrusw.res file which has some key functions like scroll up..scroll down etc...mentioned . can i modify this? if yes how will i do this. i am not used to this ASCII formatted file.
Waiting for reply.
Thanks
Rahul
|
|
|
|
| Re: Mapping Functional Keys in Forms 6i [message #84976 is a reply to message #84973] |
Sun, 16 May 2004 22:31  |
Himanshu
Messages: 457
Registered: December 2001
|
Senior Member |
|
|
Hi,
FMRPCWEB.RES or FMRWEB.RES are meant to modify Access key of Forms running on the BWE while fmrusw.res is meant for Client-Server version.
Make use of Oracle Terminal to open and Modify this file as per your Requirement.
Regards
Himanshu
|
|
|
|
| Re: Mapping Functional Keys in Forms 6i [message #84979 is a reply to message #84976] |
Mon, 17 May 2004 04:17 |
Rahul Desai
Messages: 26
Registered: March 2002
|
Junior Member |
|
|
Hi
Thanks for your suggestion. I opened the terminal and assigned user Defined key 1 with function key F2. but when i open runtime it is showing Undefined key even though the key function is shown in Show keys(ctrl+F1).
What should i do?
Thanks
Rahul
|
|
|
|
| Re: Mapping Functional Keys in Forms 6i [message #84981 is a reply to message #84979] |
Mon, 17 May 2004 06:00 |
Himanshu
Messages: 457
Registered: December 2001
|
Senior Member |
|
|
Hi,
I am psoting some Information which will help you to correctly map your Keys.
I hope you have added Key-F2 Trigger in your Form and alos chnaged the Key-Others trigger?
Regards
Himanshu
KEY MAPPINGS
Key mappings are implemented hierarchically.
Open the Oracle Forms resource file "FMRPC.RES" in Oracle Terminal, click on the "key bindings" icon (the first one), and look at the diagram in the window this creates.
You should see a diagram with one circle on the left, many circles on the right, some more circles in between, and lines connecting them like a tree. The "root" of the tree, on the left-hand side, represents the most general abstract "class" that Oracle Forms uses.
This is called "windows-sqlforms" Double-click on the circle there, and a window will appear listing some actions and the keys that are bound to them; these are the "universal" key bindings that apply whenever you are running Oracle Forms, either the designer or the runtime, no matter where you are in a forms application. Close that key bindings list, and look at the key bindings lists for "runform" and "designer".
You'll see that they have no key bindings defined on themselves; this means that they inherit all of their bindings from the "windows-sqlforms" level. This means that whenever you're in the designer, some keys will have the same functions as they do when you're in the runtime. Double-click on the circle above "listvalues" on the "runform" part of the tree. The information there tells you that when you are looking at a list- of-values in Oracle Forms Runtime, some additional keys are available for additional functions. These keys are available only when you're in a list- of-values; when you leave the list, they do not have those functions any more. If you want to change the key bindings at any level, click on a circle and press "Edit Key Bindings".
If you are looking at a list-of-values in Runform and you press a key, then Oracle Forms will look for that key's binding at the "listvalues" level of its resource file; and if it can't find the binding there it will search up through the tree for the binding until it reaches the top. If it cannot find it there then Forms will give you an "invalid function key" error. Here is an example showing how to add a key mapping to Oracle Forms, so the F3 function key on your keyboard will do an EXIT (just like Control-Q already does):
1) If you have the Forms Designer, Generator, or Runtime running right now, then quit out of them, or else Oracle Terminal will not be able to open the Forms resource file.
2) We will be editing the FMRPC.RES file, so make a backup copy of it before we begin. (You could just edit that file and save your changes as a new .RES file, except that there is a bug in Forms 4.0.12 that prevents it from using any terminal file other than FMRPC.RES.) This file is in ORAWINFORMS40.
3) Start up Oracle Terminal by double-clicking on its icon, or running "OT.EXE" from the "File Run" menu selection. When it asks you to open a file, navigate to ORAWINFORMS40 and choose "FMRPC.RES".
4) Open the key binding editor by either clicking on the "K key" icon, picking the "Functions Edit keys" menu selection, or pressing Control-M.
5) Double-click on the circle above "windows-sqlforms (at the left edge of the window), or click once on it and press "Edit Key Bindings". This brings up a window showing you the keys that are universally mapped across all of the Oracle Forms tools (since you are showing the key mappings list for the highest level of the hierarchy).
6) Click on the "Insert Row" button. This adds another line for you to put a new key binding on. 7) Enter the word "Exit" on your new row in the Action column (you must type it with a capital "E" and lower-case "xit"), and enter "F3" in the "Binding" column.
8) Click "OK" to return to the key binding editor.
9) Make sure that the F3 key is not mapped to something else lower in the hierarchy, by double-clicking on each of the circles to the right of "windows-sqlforms" and making sure that F3 is not shown in the list of key bindings. If you do find it in the key bindings for another level, then delete it with the "Delete Row" button.
10) Click "OK" to dismiss the key binding editor when you are finished with it.
Now that you've added a new key binding, you need to generate and save it before you can use it:
1) Click on the "generate" button (the meat grinder, the rightmost icon), pick the "Functions Generate" menu selection, or press Control-G. If it asks you if you want to save your changes before you generate, then choose "yes". After it generates, it should display a dialog box telling you that the generate completed successfully.
2) Save your changes by picking the "File Save" menu selection, and exit Oracle Terminal by picking "File Exit". Note: Both of the save actions mentioned above (before the generate and after the generate) are necessary; the first action saves the structire changes which are necessary to perform the generate successfully, and the second save saves the fully generated, complete file. Now try starting up Forms Runtime, and pressing F3 to see if it successfully exits the application. F3 should also appear when you tell Forms to "Show Keys". You can map many keystrokes all to the same action, but you cannot map one specific keystroke to more than one action.
PRODUCT ACTIONS
You can only bind a keypress to an action that's available at a given level of Oracle Forms. Sometimes you will want to define a key for an action that does not already exist at that level, so you will have to add the action. A list at the end of this bulletin shows many of the actions that Oracle Forms recognizes and can respond to. You can add these actions to any level of the Oracle Forms tools and bind keys to them to make them useable. Here is an example of how to define the "User Defined Key 2" action in Oracle Forms Runtime, and bind it to the F2 key:
1) Close any Oracle Forms tools (Designer, Generate, Runtime) that you might have running, so you can modify their resource file without getting any "file already open" errors.
2) You will be editing ORAWINFORMS40FMRPC.RES, so make a backup copy of it for safekeeping.
3) Run Oracle Terminal, and open FMRPC.RES.
4) Go into the key binding editor, and click on the "Product Actions" button. This brings up the Product Actions Editor, which looks like the Key Bindings Editor.
5) Double-click on the circle above the word "runform". This brings you to the Product Action definition screen.
6) Insert a new row by clicking on the "Insert Row" button.
7) Put the phrase "User Defined Key 2" in the Action column, and put 84 in the Code column.
8) Click "OK" to dismiss the Product Action dialog, then click "OK" in the Product Action Editor to dismiss it too.
Now you have made that action available for the level you are editing. All that remains is to bind a key to it, to make it useful.
Here's a summary of the instructions given above for how to add a key binding:
1) In the Key Binding Editor, double-click on the "runform" circle.
2) Press the "Insert Row" button, and define a new binding with action "User Defined Key 2" and binding "F2". Click "OK" to close the Key Binding Definition window.
3) Make sure that the "F2" key is not bound at any other level below "runform" by checking the Key Binding Definition entries for all circles connected to "runform" to the right of it.
4) Press the "OK" button to dismiss the Key Binding Editor, and generate the new key bindings by clicking on the Generate icon in the FMRPC.RES window. Save your new bindings by selecting "Save" from the File menu.
5) Exit Oracle Terminal, and test this new action by putting a KEY-F2 trigger in a form and using Runform to make sure that it works.
Regards
Himanshu
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
