home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!mimsy!afterlife!dpkemp
- From: dpkemp@afterlife.ncsc.mil (David P. Kemp)
- Newsgroups: alt.toolkits.xview
- Subject: Devguide 3.0 generates excessive menu code?
- Message-ID: <1993Jan3.014814.22437@afterlife.ncsc.mil>
- Date: 3 Jan 93 01:48:14 GMT
- Organization: The Great Beyond
- Lines: 29
-
- Is there any way to coerce the Devguide 3.0 connection manager to
- create a MENU_NOTIFY_PROC?
-
- Under the connection manager, I specify a source and target menu item,
- specify When: Notify, and Op: CallFunction. In response to this, gxv
- generates a MENU_GEN_PROC entry in xxx_ui.h, and a huge (well, ~15 lines)
- block of code for *each* menu item in xxx_stubs.c. Each code block
- contains a switch selecting actions from MENU_DISPLAY, MENU_DISPLAY_DONE,
- MENU_NOTIFY, and MENU_NOTIFY_DONE.
-
- The proper behavior can be attained by putting code inside the MENU_NOTIFY
- section of the switch, but there is certainly a lot of extra rubbish
- hanging around for no reason. All that extra code and all those extra
- calls could be avoided if gxv would just generate a MENU_NOTIFY_PROC
- instead of a MENU_GEN_PROC in the first place.
-
- This is not really a big deal, since memory is cheap and cycles are
- getting faster each year. I just find it offensive that the tools we
- use to develop applications encourage such waste for no reason.
-
- Am I misusing Devguide?
- If not, can this be fixed an a future release?
- Or should we all forget about Xview and switch to OLIT?
-
- --
- Dave Kemp dpkemp@afterlife.ncsc.mil
- -----------------------------------------------------------------------------
- "Washington [D.C.] is a city of Southern efficiency and Northern charm"
- -- John F. Kennedy
-