Topic Unconditional using a Group.
We have two new locations for Keyman technical support:
The Tavultesoft Forums are now read only.
| # Unconditional using a Group.   2016-02-26 03:46:59.860 | 
|---|
br Julian Griffin OSL
  | As I understand it, any group can only have a maximum of two Rules that fire in one iteration. One on a Context (with or without a key press) and one on a Match/Nomatch, and after this the Group is exited.
 
   If I have read it correctly, Match & Nomatch are not the exact inverse of one another.
 
   My question is, is there a way to chain Groups unconditionally?
 
   Something like a simple  
 as the last line in a Group.
 
 
	  | : | 
	 
	
	  Match   > Use(NextGroup)
 
Nomatch > Use(NextGroup) | 
	 
 
   Could not be relied on to always jump to Group(NextGroup).
 
Regards
 
Julian Griffin  | 
| # RE: Unconditional using a Group.   2016-02-26 07:55:57.550 | 
|---|
Marc Durdin Tavultesoft Staff | Yes, you have a correct understanding. The gap between match and nomatch is to do with how nomatch handles non-character keys for 'using keys' groups. It turns out that for most keyboards, if a key such as /F12/ is pressed, you don't want it to be handled in a nomatch rule. Conversely, if the key would normally generate a character on the system keyboard, it should fire the nomatch.
 
 
However, there are cases where this would be desirable, such as for a preprocessing group, and I do have an issue in the queue to add this as a feature, tentatively called nomatch(all). Not sure when/if this will happen though.
 
 
For context-only groups, match and nomatch are exact inverse.  |