| Playing with Scan Codes |
| QTIPS - Compiling Protection Code |
| QTIPS - Invalid Code and Command |
| QTIPS - Code/Command Help |
| Compiling 64K on a Shoestring by Blaise Wrenn (LexStat Systems Ltd) |
| Reader's Clinic - Capture Command and Captured Keystrokes |
| Catalyst |
| Popups |
| Catalyst Tips |
| QTIPS - NoRead |
| Reader's Clinic - EVAL |
| QTIPS - New Catalyst Option |
| Argument passing - Subroutines and Functions - Mike Pope |
| Caching in on the Frames Array - Mike Pope |
| QTIPS - Fast Dynamic Array Building |
| Version 3 Technical Highlights - INRECT |
| Version 3 Technical Highlights - Input.Char |
| QTIPS - Calling an Action Bar from a Pulldown Menu |
| Reader's Clinic - Line Length > 256 Characters |
| QTIPS - String Space |
| QTIPS - String Space Format Errors |
| Reader's Forum - Numeric Precision in R/Basic - Hal Wyman |
RevMedia FKB
| Document | V4I8A8 |
| Title | QTIPS - Calling an Action Bar from a Pulldown Menu |
| Keywords | PULLDOWN_WINUS MENU INRECT |
| Text | Dave Mills continues "This can be easily accomplished Cascading pulldown menus are achieved by AREV by recursive CALLS to Pulldown_Winus Pulldown_winus only recognises a code of "M" for this all other CALLS are passed to Catalyst The following CALLS all result in the display of an Action Bar menu Code Command MP MenuName X RunMenu MenuName M;M Menu1;Menu2 S;M Subroutine;MenuName MP is least messy The P modifier only suspends playback of captured keystrokes " Editor's note As Dave points out ANY code other than M is passed to Catalyst thus any modifier may be used If you don't want to suspend playback then use a ! or similar character which will just be ignored The additional values of the MenuLevel dynamic array in 3 0 are as follows < 1 > Menu level < 2 1 > Xpos < 2 2 > Ypos < 3 > When in the first level of Pulldown FROM an action bar it is possible to arrow left and right and move between menus without returning to the action bar This field is set to either the scan code for CURSOR right or the scan code for CURSOR left so that the CALLING program can know which way the user has opted to move If you are CALLING Pulldown_Winus DIRECTLY (or you have shelled it) you can take advantage of this information < 4 > Only seems to be set to true when < 3 > is set < 5 > The X position of the previous menu < 6 > INRECT location string (see REVMEDIA passim) which on entry to Pulldown_Winus contains the location of the previous pulldown menu along WITH a string of 0 0 0 0 coordinates for each subsequent menu level < 7 > INRECT location string for the menu line just selected < 8 > Not used < 9 > Not used < 10 > Unable to determine (Volume 4 Issue 8 Pages 11 12) |
Page last modified: 31/01/03