1. PLANS
- Posted by Vorn Mom <vornet at ICI.NET>
Feb 09, 1997
-
Last edited Feb 10, 1997
I am planning on creating an include file called MENU.E
which can be added to any program to have the looks
and feels of EDIT.COM, or QBASIC.COM. Easy to
implant to any program. It will have mouse functionallity (optional
though),
and keyboard.
Available soon...
2. PLANS
- Posted by Ad Rienks <Ad_Rienks at COMPUSERVE.COM>
Feb 09, 1997
-
Last edited Feb 10, 1997
>Poster: Vorn Mom <vornet at ICI.NET>
>Subject: PLANS
>--------------------------------------------------------------------------
-----
>I am planning on creating an include file called MENU.E
>which can be added to any program to have the looks
>and feels of EDIT.COM, or QBASIC.COM. Easy to
>implant to any program. It will have mouse functionallity (optional
>though),
>and keyboard.
>Available soon...
I' m *very* interested. At the moment I'm using the text GUI routines by
David Cuny.
Did you see that? Will your contribution be similar to his? Maybe we can
throw all good efforts together in this, there is no use in reinventing the
wheel, isn't it?
Hope to hear from you soon!
Ad Rienks
3. PLANS
*** Reply to note of 02/10/97 15:52
hmm... our system went off-line for a while, so i'm only seeing this
response, and not the initial message.
yes, you get the same features from the tools in my gui toolkit. i've
just added mouse functions to all the features (although the mouse drag
is a bit problematic on my slow 386 - i may make it optional).
if you want to use the menu stuff without all the other baggage in the
toolkit, you can comment out the line:
include dialog.ex
and copy the definitions for the following from dialog.ex into menu.ex:
constant ALPHA_ALT_KEYS ... -- used to convert keys to alt keys
constant NUMERIC_ALT_KEYS ... -- and number keys to alt equivalents
function normal_to_alt() ... -- uses prior tables to match normal keys
-- with their alt-key equivalents
and you don't have to use anything else in the toolkit.
-- david cuny
