adding my $.02: VASL has relied on 'honor-code' wrt LOS checks. I've no objection to checks becoming part of the logfile or ftf game, reported/displayed to the opponent when the down-click is released. Two (VASL-specific?) probs occur to me: a) When the LOS-initiator player down-clicks on a hex, and holds down while moving the end-point, he is able to check LOS to multiple hexes, and the CASL-derived LOS-blockage/hindrance msgs appear on his screen, before he releases his click. In the proposed model, these msgs should be suppressed until the click is released. b) Once the click is released, the initiator might need to use various kbd-cmds to move the origin or endpoint of the LOS-thread to the desired in-hex vertical level. This would req: 1) initiate LOS mode 2) down-click on source hex 3) up-click on end hex 4) allow kbd-cmds to adjust vertical level in source/end hex 5) kbd-cmd to initiate display of CASL LOS msgs. NTM it's possible that a HIP/Invisible unit could impact the LOS - presumably they could be revealed as req'd.
------------------------ Yahoo! Groups Sponsor --------------------~--> Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/IMSolB/TM --------------------------------------------------------------------~-> 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/
