Re: Forms 4.0 : Questions on transition
Date: Tue, 8 Mar 1994 03:33:08 GMT
Message-ID: <SMUENCH.94Mar7193308_at_doh.oracle.com>
SEAN -- To say that your key triggers "become completely invalid" is
incorrect and misleading. You are neither forced to remove key
triggers, nor forced to recode them in button triggers.
Our upgrade utility takes your 3.0 application and brings it
intact to 4.0, preserving all of your code, logic, screens,
etc. There's no reason a bitmapped user would *not* want to
use the keys, but there is a *big* reason why they might want
to use the mouse. So, you can code new functionality to
hook into the existing key-driven logic with Buttons and Menu
Items that exercise the key-logic with the DO_KEY() built-in.
The one optional thing you might consider regarding key
triggers is removing block-coordination logic and adding the
new, more-powerful, relation object into your form. This will
coordinate arbitrarily complex hierarchical relationships
(with declarative coordination behavior that changeable
programmatically at runtime) driven *either* by the keys or by
the mouse.
You could call Forms 3.0 from Forms 4.0, but you'd have to
spawn an 'xterm' window to run it in. The '-e' flag to xterm
would let you run whatever command you need, including 'iap30'.
Hope this clears things up.
-- Steve Muench Email: smuench_at_oracle.com Forms Development CIS: 73404,676 Product Manager Oracle CorporationReceived on Tue Mar 08 1994 - 04:33:08 CET