Forms 6i y Oracle Terminal

Quiero modificar la definicion de ciertas funciones de teclado. En los manuales habla del Oracle Terminal pero no se lo que es y donde esta instalado o si hay que hacerlo. ¿Alguien sabe de que se trata? Tambien mi duda es sobre como trabajar con los trigers de tipo KEY-Fn (n=1,2...).

1 Respuesta

Respuesta
1
Existe una respuestra que di a alguien acerca de esto, te copio el ultimo mensaje:
Esto lo encuentras en metalink:
Customising the Resource File
---------------------------------------------
The resource file, fmrweb. Res is a text file which can edited via a simple editor such
as vi on Unix or Notepad/ Wordpad on MS Windows.
Oracle Terminal editor is NO longer required. The text file contains documentation
and is relatively self explanatory.
Note: the customisation is limited, particularly compared to character mode forms.
An simple example change: Swapping Enter and Execute mappings around:
# 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.
#
..
122 : 0 : "F11" : 76 : "Enter Query"
122 : 2 : "Ctrl+F11" : 77 : "Execute Query"
Change to:
122 : 2 : "Ctrl+F11" : 76 : "Enter Query"
122 : 0 : "F11" : 77 : "Execute Query"
Note: By default fmrweb. Res does NOT reflect the MS Windows client-server keyboard
mappings. Rather it reflects the key mapping if running client-server on Unix X-Windows/ Motif.
A file called fmrpcweb. Res has also been provided which does give the MS Windows
client-server keyboard mappings. To use this file, rename fmrweb.res e.g to fmrweb_orig. Res,
and copy fmrpcweb. Res to fmrweb. Res. Alternatively use the term parameter as described above.
Exceptions/ Special Key Mappings
--------------------------------------------------
A: Mapping F2
Change the default entry for F2, "List Tab Pages", to another key.
Here is an example of the default entry:
113: 0 : "F2" : 95 : "List Tab Pages"
This must be explicitly changed to another key mapping such as the following:
113: 8 : "F2" : 95 : "List Tab Pages"
To map the F2 function to the F2 key, comment out the lines that
begin with "113 : 0" and "113 : 3" with a # symbol and add the following lines
to the bottom of the resource file.
113: 0 : "F2" : 84 : "Function 2"
113: 8 : " " : 95 : " "
Explanation:
A new function has been added which uses F2 by default It is necessary to explicitly
map this new function to something else in order to map the F2 key." This function
was added to allow for keyboard navigation between the tab canvas pages and it
defaults to F2. Even if it is commented out and not assigned to F2, the F2 key
cannot be mapped unless this function, Forms Function Number 95, is mapped to
another key.
B: Mapping for ENTER to fire KEY-ENTER-TRIGGER over the Web
By default, whether deploying

Añade tu respuesta

Haz clic para o

Más respuestas relacionadas