Well, I tried screwing around with that and it doesn;t seem to change anything. Putting the report action first still makes the GKC and the reports associated with it happen first. As for my temporary solution, am I right in thinking that the updated version will let you have unnamed GKCs? If that's the case, I can get rid of the extra menu items and it's no problem. Thanks for the help.
-Matt --- In [email protected], Rodney Kinney <[EMAIL PROTECTED]> wrote: > > You should be able to control this by changing the relative order of the > Report Action and Global Key Command traits. > > rk > > > Another quick question. In my module, Piece A has a Global Key > > Command, and a Report Action that announces when it executes that > > GKC's command. Now, the recipients of the GKC also have a Report > > ACtion so they announce when they've received it. However, as it > > stands now, the message received signal gets to the main window before > > the message sent signal. Is there any way around that? I can do it by > > linking Piece A's report to a Trigger Action that also triggers the > > GKC, but then I've got an extra menu item that's just cluttering > > things up. Any better suggestions would be welcome. Thanks. > > > > > > > [Non-text portions of this message have been removed] > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/vassalengine/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
