OraFAQ Forum: Forms » associating keys with triggers

Home » Developer & Programmer » Forms » associating keys with triggers

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

associating keys with triggers [message #141979]

Thu, 13 October 2005 00:17

naveednt
Messages: 34
Registered: October 2005
Location: Karachi, Pakistan

Member

I want to associate some keys with some triggers in my application through Oracle Terminal.
Oracle Terminal is not accepting Undo as an Action
for example, associating F11 with a User-named trigger 'UNDO'.
any help will be appricated.

Thanks in Advance

Report message to a moderator

Re: associating keys with triggers [message #141984 is a reply to message #141979]

Thu, 13 October 2005 01:25

djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia

Senior Member
Account Moderator

I don't think there is a 'thing' called 'UNDO' in Oracle.

Does your documentation have a list of valid operations? Is UNDO among them?

David

Report message to a moderator

Re: associating keys with triggers [message #142006 is a reply to message #141984]

Thu, 13 October 2005 02:29

naveednt
Messages: 34
Registered: October 2005
Location: Karachi, Pakistan

Member

I think I did'nt ask the question correctly.
Actually pre-defined triggers are associated with pre-defined events. we can add user-named triggers, but I think can not create new events to associate with user-named triggers.
The name of the trigger establishes the association between the event and the trigger code.

so, I m reasking my question
I want to associate a specified event with specified key.
like KEY-EXEQRY associated with F8, KEY-PRINT with Shift+F8, KEY-COMMIT with F10.

my requirment is MYTRIGGER1 or UNDO with F11

I can change the default keys for pre-defined triggers, I can change KEY-EXEQRY's association from F8 to F11 or some other keys available.

Report message to a moderator

Re: associating keys with triggers [message #142012 is a reply to message #142006]

Thu, 13 October 2005 02:34

djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia

Senior Member
Account Moderator

If it is not associated with any pre-defined action then just use the 'key-Fnn' trigger. In this case, use the Key-F11 trigger.

David

Report message to a moderator

Re: associating keys with triggers [message #142254 is a reply to message #142012]

Thu, 13 October 2005 23:43

naveednt
Messages: 34
Registered: October 2005
Location: Karachi, Pakistan

Member

key Fnn Triggers are limited to key-F9.

is that mean, it is not possible in Developer?

Report message to a moderator

Re: associating keys with triggers [message #142258 is a reply to message #142254]

Fri, 14 October 2005 00:03

djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia

Senior Member
Account Moderator

Oops ... my bad ... I was looking at the DO_KEY doco.

Quote:

DO_KEY restrictions

DO_KEY accepts built-in names only, not key names: DO_KEY(ENTER_QUERY). To accept a specific key name, use the EXECUTE_TRIGGER built-in: EXECUTE_TRIGGER('KEY_F11').

Your previous response:

Quote:

I think can not create new events to associate with user-named triggers.
The name of the trigger establishes the association between the event and the trigger code.

is true. But what you can do is write your own code inside those currently defined triggers. For example, if you were able to move 'KEY-EXEQRY' from F8 to F11 then to program F11 write your code in the 'KEY-EXEQRY' trigger and then write new code in the 'Key-F8' trigger which does an 'Execute_trigger'.

Try this and get back to us.

David

Report message to a moderator

Re: associating keys with triggers [message #142266 is a reply to message #142258]

Fri, 14 October 2005 00:42

naveednt
Messages: 34
Registered: October 2005
Location: Karachi, Pakistan

Member

thanks a lot, but I have already worked on that ... and its useless if I need both .. F8 on key-exeqry and F11 on another

Report message to a moderator

Re: associating keys with triggers [message #142269 is a reply to message #142266]

Fri, 14 October 2005 00:51

djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia

Senior Member
Account Moderator

You missed my point. If F8 WAS Execute_Query and you can move Execute_Query to F11 using Oracle Terminal, then F11 will fire the Key-EXEQRY trigger in which you place your OWN code which does NOT do an execute_query and you program Key-F8 to do an Execute_Query.

Have you searched this forum or google for 'frmweb.res' and 'frmpcweb.res'? These are files in which Oracle Terminal makes its changes.

David

Report message to a moderator

Re: associating keys with triggers [message #142271 is a reply to message #142266]

Fri, 14 October 2005 00:58

djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia

Senior Member
Account Moderator

To test which keys are firing create a form called pfkeys, add ALL the 'key-' triggers at the form level, first Key- trigger is Key-CLRBLK and contains "message('KEY-CLRBLK');". Add every other 'Key-' trigger with a matching message statement. You will need a single accessable item in a block on a canvas but you don't use it. Compile and run the form, and when you press your various function keys it will tell you the Oracle Forms facility that matches it. Five minutes work that will save you 100 times the time further down the track.

David

Report message to a moderator

Re: associating keys with triggers [message #142272 is a reply to message #142269]

Fri, 14 October 2005 01:00

naveednt
Messages: 34
Registered: October 2005
Location: Karachi, Pakistan

Member

I think again I was unable to convay, what I was trying to say..
I am telling that,

If
F11 is replaced in place of F8 then, key-exeqry will be executed after pressing F11 (not F8).
and in this way F8 has no association.

I mean .. one trigger(key-exeqry) with more two keys(F8, F11)
of
limited triggers / events with unlimited keys.

Report message to a moderator

Re: associating keys with triggers [message #142273 is a reply to message #142272]

Fri, 14 October 2005 01:02

naveednt
Messages: 34
Registered: October 2005
Location: Karachi, Pakistan

Member

in addition, I can associate any key to available triggers/events but I adding new events is nearly impossible to me

Report message to a moderator

Re: associating keys with triggers [message #142281 is a reply to message #142273]

Fri, 14 October 2005 01:21

djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia

Senior Member
Account Moderator

Have you searched this forum for 'oracle terminal'? There are various threads and one contains a Metalink Note ID which may be helpful.

By the way, which version of Forms are you running?

David

Report message to a moderator

Re: associating keys with triggers [message #142282 is a reply to message #142281]

Fri, 14 October 2005 01:26

djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia

Senior Member
Account Moderator

Yea ... Metalink Note:209671.1 - "How to Change / Customize the Key Mappings for 6i and 9.x Webforms?" looks like the document you guys need to read.

David

Report message to a moderator

Re: associating keys with triggers [message #142288 is a reply to message #142282]

Fri, 14 October 2005 01:36

naveednt
Messages: 34
Registered: October 2005
Location: Karachi, Pakistan

Member

and how to access that metalink... its only accessible to reg. users only.

Report message to a moderator

Re: associating keys with triggers [message #142292 is a reply to message #142288]

Fri, 14 October 2005 01:41

djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia

Senior Member
Account Moderator

Okay ... this is my 4.5 frmweb.res ... what does yours look like? Use Notepad to open it.

#  FMRWEB.RES is the key definition file for webforms. The syntax is:
#
#    JFN : JMN : URKS : FFN : URFD   (whitespace ignored)
#
#      JFN = Java function number
#      JMN = Java modifiers number
#     URKS = User-readable key sequence (double-quoted)
#      FFN = Forms function number
#     URFD = User-readable function description (double-quoted)
#
#  JAVA FUNCTION NUMBER
#         33 = PageUp
#         34 = PageDown
#         35 = End
#         36 = Home
#         37 = LeftArrow
#         38 = UpArrow
#         39 = RightArrow
#         40 = DownArrow
#    65 - 90 = Ctrl+A thru Ctrl+Z (These will always have the control
#              modifier explicitly included, as well as any other
#              modifiers that might be used.)
#  112 - 123 = F1 thru F12
#          9 = Tab (Ctrl+I, without the control modifier)
#         10 = Return (Ctrl+J, without the control modifier)
#
#  JAVA MODIFIERS NUMBER
#  Equal to the sum of the values for the modifier keys:
#    0 = None
#    1 = Shift
#    2 = Control
#    4 = Meta
#    8 = Alt
#
#  FORMS FUNCTION NUMBER
#  The Forms function numbers match the function numbers found in a
#  typical Forms key binding file.
#
#  USER-READABLE STRINGS 
#  The double-quoted strings appear when users click [Show Keys], and
#  are used for this purpose only. These strings can be translated as
#  needed. Note that the strings do not affect what actually happens
#  when end users press a particular key sequence.
#
9    : 0 : "Tab"            : 1  : "Next Field"
9    : 1 : "Shift+Tab"      : 2  : "Previous Field"
116  : 0 : "F5"             : 3  : "Clear Field"
38   : 0 : "Up"             : 6  : "Up"
40   : 0 : "Down"           : 7  : "Down"
33   : 0 : "PageUp"         : 12 : "Scroll Up"
34   : 0 : "PageDown"       : 13 : "Scroll Down"
69   : 2 : "Ctrl+E"         : 22 : "Edit"
10   : 0 : "Return"         : 27 : "Return"
76   : 2 : "Ctrl+L"         : 29 : "List of Values"
115  : 0 : "F4"             : 32 : "Exit"
75   : 2 : "Ctrl+K"         : 35 : "Show Keys"
83   : 2 : "Ctrl+S"         : 36 : "Commit"
118  : 1 : "Shift+F7"       : 61 : "Next Primary Key"
117  : 0 : "F6"             : 62 : "Clear Record"
38   : 2 : "Ctrl+Up"        : 63 : "Delete Record"
117  : 1 : "Shift+F6"       : 64 : "Duplicate Record"
40   : 2 : "Ctrl+Down"      : 65 : "Insert Record"
119  : 1 : "Shift+F8"       : 66 : "Next Set of Records"
1005 : 0 : "Down"           : 67 : "Next Record"
1004 : 0 : "Up"             : 68 : "Previous Record"
118  : 0 : "F7"             : 69 : "Clear Block"
66   : 2 : "Ctrl+B"         : 70 : "Block Menu"
34   : 1 : "Shift+PageDown" : 71 : "Next Block"
33   : 1 : "Shift+PageUp"   : 72 : "Previous Block"
116  : 1 : "Shift+F5"       : 73 : "Duplicate Field"
119  : 0 : "F8"             : 74 : "Clear Form"
122  : 0 : "F11"            : 76 : "Enter Query"
122  : 2 : "Ctrl+F11"       : 77 : "Execute Query"
69   : 3 : "Shift+Ctrl+E"   : 78 : "Display Error"
80   : 2 : "Ctrl+P"         : 79 : "Print"
123  : 0 : "F12"            : 80 : "Count Query"
85   : 2 : "Ctrl+U"         : 81 : "Update Record"
121  : 3 : "Shift+Ctrl+F10" : 82 : "Function 0"
112  : 3 : "Shift+Ctrl+F1"  : 83 : "Function 1"
113  : 3 : "Shift+Ctrl+F2"  : 84 : "Function 2"
114  : 3 : "Shift+Ctrl+F3"  : 85 : "Function 3"
115  : 3 : "Shift+Ctrl+F4"  : 86 : "Function 4"
116  : 3 : "Shift+Ctrl+F5"  : 87 : "Function 5"
117  : 3 : "Shift+Ctrl+F6"  : 88 : "Function 6"
118  : 3 : "Shift+Ctrl+F7"  : 89 : "Function 7"
119  : 3 : "Shift+Ctrl+F8"  : 90 : "Function 8"
120  : 3 : "Shift+Ctrl+F9"  : 91 : "Function 9"

What version of forms are you running?

David

Report message to a moderator

Re: associating keys with triggers [message #142293 is a reply to message #142292]

Fri, 14 October 2005 01:46

naveednt
Messages: 34
Registered: October 2005
Location: Karachi, Pakistan

Member

#  FMRWEB.RES is the key definition file for webforms. The syntax is:
#
#    JFN : JMN : URKS : FFN : URFD   (whitespace ignored)
#
#      JFN = Java function number
#      JMN = Java modifiers number
#     URKS = User-readable key sequence (double-quoted)
#      FFN = Forms function number
#     URFD = User-readable function description (double-quoted)
#
#  JAVA FUNCTION NUMBER
#         33 = PageUp
#         34 = PageDown
#         35 = End
#         36 = Home
#         37 = LeftArrow
#         38 = UpArrow
#         39 = RightArrow
#         40 = DownArrow
#    65 - 90 = Ctrl+A thru Ctrl+Z (These will always have the control
#              modifier explicitly included, as well as any other
#              modifiers that might be used.)
#  112 - 123 = F1 thru F12
#          9 = Tab (Ctrl+I, without the control modifier)
#         10 = Return (Ctrl+J, without the control modifier)
#
#  JAVA MODIFIERS NUMBER
#  Equal to the sum of the values for the modifier keys:
#    0 = None
#    1 = Shift
#    2 = Control
#    4 = Meta
#    8 = Alt
#
#  FORMS FUNCTION NUMBER
#  The Forms function numbers match the function numbers found in a
#  typical Forms key binding file.
#
#  USER-READABLE STRINGS 
#  The double-quoted strings appear when users click [Show Keys], and
#  are used for this purpose only. These strings can be translated as
#  needed. Note that the strings do not affect what actually happens
#  when end users press a particular key sequence.
#
9    : 0 : "Tab"            : 1  : "Next Field"
9    : 1 : "Shift+Tab"      : 2  : "Previous Field"
116  : 0 : "F5"             : 3  : "Clear Field"
38   : 0 : "Up"             : 6  : "Up"
40   : 0 : "Down"           : 7  : "Down"
33   : 0 : "PageUp"         : 12 : "Scroll Up"
34   : 0 : "PageDown"       : 13 : "Scroll Down"
69   : 2 : "Ctrl+E"         : 22 : "Edit"
10   : 0 : "Return"         : 27 : "Return"
76   : 2 : "Ctrl+L"         : 29 : "List of Values"
115  : 0 : "F4"             : 32 : "Exit"
75   : 2 : "Ctrl+K"         : 35 : "Show Keys"
83   : 2 : "Ctrl+S"         : 36 : "Commit"
118  : 1 : "Shift+F7"       : 61 : "Next Primary Key"
117  : 0 : "F6"             : 62 : "Clear Record"
38   : 2 : "Ctrl+Up"        : 63 : "Delete Record"
117  : 1 : "Shift+F6"       : 64 : "Duplicate Record"
40   : 2 : "Ctrl+Down"      : 65 : "Insert Record"
119  : 1 : "Shift+F8"       : 66 : "Next Set of Records"
1005 : 0 : "Down"           : 67 : "Next Record"
1004 : 0 : "Up"             : 68 : "Previous Record"
118  : 0 : "F7"             : 69 : "Clear Block"
66   : 2 : "Ctrl+B"         : 70 : "Block Menu"
34   : 1 : "Shift+PageDown" : 71 : "Next Block"
33   : 1 : "Shift+PageUp"   : 72 : "Previous Block"
116  : 1 : "Shift+F5"       : 73 : "Duplicate Field"
119  : 0 : "F8"             : 74 : "Clear Form"
122  : 0 : "F11"            : 76 : "Enter Query"
122  : 2 : "Ctrl+F11"       : 77 : "Execute Query"
69   : 3 : "Shift+Ctrl+E"   : 78 : "Display Error"
80   : 2 : "Ctrl+P"         : 79 : "Print"
123  : 0 : "F12"            : 80 : "Count Query"
85   : 2 : "Ctrl+U"         : 81 : "Update Record"
121  : 3 : "Shift+Ctrl+F10" : 82 : "Function 0"
112  : 3 : "Shift+Ctrl+F1"  : 83 : "Function 1"
113  : 3 : "Shift+Ctrl+F2"  : 84 : "Function 2"
114  : 3 : "Shift+Ctrl+F3"  : 85 : "Function 3"
115  : 3 : "Shift+Ctrl+F4"  : 86 : "Function 4"
116  : 3 : "Shift+Ctrl+F5"  : 87 : "Function 5"
117  : 3 : "Shift+Ctrl+F6"  : 88 : "Function 6"
118  : 3 : "Shift+Ctrl+F7"  : 89 : "Function 7"
119  : 3 : "Shift+Ctrl+F8"  : 90 : "Function 8"
120  : 3 : "Shift+Ctrl+F9"  : 91 : "Function 9"
113  : 0 : "F2"             : 95 : "List Tab Pages"
72   : 2 : "Ctrl+H"         : 30 : "Help"

using 6i

[Updated on: Fri, 14 October 2005 01:47] by Moderator

Report message to a moderator

Re: associating keys with triggers [message #142295 is a reply to message #142293]

Fri, 14 October 2005 01:50

djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia

Senior Member
Account Moderator

Does making changes to this file have any affect on your form's function key behaviour?

Have your coded the pfkeys form yet?

David

Report message to a moderator

Re: associating keys with triggers [message #142310 is a reply to message #142295]

Fri, 14 October 2005 02:15

naveednt
Messages: 34
Registered: October 2005
Location: Karachi, Pakistan

Member

no i think this file is for web based forms key bindings.

if u open fmrusw.res in ot and press the button 'Edit key bindings for product actions' there u have trhee buttons
1) Product actions...
2) preview key bindings...
3) edit key bindings...

if you go into product actions, and double-click any node .. (i.e runform --> normal)
there u will have three columns
action, code, description
action is used for binding the key where we will define action and key. (pressing button 2 in previous window will get u there)
string u type in description will visible in Shift+F1 list at runtime.

the codes defined in the 'code' column are (I think) refering the events / triggers in forms, I have inserted a new row with a new code, but its useless.

don't know where to associate new codes with events / triggers

Report message to a moderator

Previous Topic:	very urgent - How to make connection to SQL Server
Next Topic:	Problem in blocks and canvas

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Sep 20 10:25:16 CDT 2024