REVMEDIA FKB Articles - AREV, OI, REV G, jREV, JCDC, LIVEWATER,ADVANCED REVELATION, OPENINSIGHT, REVELATION G

RevMedia FKB

Document	V3I10A13
Title	Uncommon Knowledge - WC_Unkeys%
Keywords	WINDOW_COMMON% WC_UNKEYS% EDIT.KEYS WC_WEXIT_KEYS% WC_EXCEPT_KEYS%
Text	A field mark delimited list of keys which are to be disabled in the window Primarily used to link to the "Key Disable" option in Paint This variable is used by the system to modify WC_WExit_Keys% and WC_Except_Keys% (q v ) by swapping out the appropriate scan codes for the literal "!!" in these variables Thus once these VARIABLES have been changed they are no longer affected by the contents of WC_UnKeys% As this swapping seems to be done AFTER the Pre_Init process it is possible to amend WC_UnKeys% at the Pre_Init process by DIRECTLY modifying @RECORD which contains the CURRENT template record This has the effect of changing the disabled keys in the window Note that this means that WC_UnKeys% can only be effectively modified at the Pre Init stage AFTER this it is not referenced again Note further that the same effect could be achieved anywhere in the window by swapping the appropriate scan codes for the literal "!!" in WC_WExit_Keys% and WC_Except_Keys% (q v ) In either case rather than looking for the scan code itself one should use the EDIT KEYS include record look to ensure that if the user has remapped the keyboard that the scan code will still be found There follows an EXAMPLE piece of code to illustrate the use of WC_UnKeys% in a pre init process Subroutine Kill_Refresh $Insert Include Edit Keys Equ Dlm$ To Char(247) * Get Unkeys FROM @Record FROM pos 43 delimited by char(247)s Un = Field(@Record Dlm$ 43) Un< 1> = Refresh Key @Record=Fieldstore(@Record Dlm$ 43 1 Un) Return Normally this should be sufficient however under some circumstances (such as WITH some collector windows and some releases of the software) this might not be enough as Curt Putnam points out "the window processor sets flags within the body of the template record to indicate whether there are any further options to process" This helps speed up the loading process These flags are referred to in the TEMPLATE record in UTILITY DOC as OPTIONS1 and OPTIONS2 and are found in positions 20 and 35 respectively (delimited by char(247)s) Normally these FLAGS are ALWAYS set as the system sets recalculate options and WC_Atr_Ovr% automatically upon save and this is enough to trigger them If however you FIND that the above code does not work on the release of AREV you are working WITH try amending it by inserting the following two lines after the @Record = FIELDSTORE LINE * Set Options1 @Record=Fieldstore(@Record Dlm$ 20 1 1) * Set Options2 @Record=Fieldstore(@Record Dlm$ 35 1 1) (Volume 3 Issue 10 Pages 11 12)

[revmedia/copyrigh.htm]

Page last modified: 08/02/03