Comments below, Cheers, Brent.
*********** REPLY SEPARATOR *********** >On 28/12/2005 at 4:52 AM countermancx wrote: >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. No, in the proposed model, the LOS thread works identically to the way it does now, only the last LOS check is reported. Though that is an idea, while the mouse is down, no thead is extended, but a circle highlighting the end-point follows the cursor. When the mouse is released, the thread is drawn. Perhaps this could be an optional 'mode'. Yes, multiple LOS checks to various hexes will not be reported, but at least the fact that a LOS check has been performed from a given hex is announced. If the attacker announces he is attacking from hex A to hex B first BEFORE the LOS check is announced, then it is not such a great problem. Yes, there is still room to break the spirit (Hmm, While checking A to B, I'll also check A to C in case I want to attack there later). Of course, any serious cheater will just have another vassal session open in another window and do all his LOS check there. The other use for this feature that has been alluded to is that it will provide an 'I am attacking from here to here' indication >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. The point is not to report the success/failure of the LOS check, but to report that an LOS check from a given hex has occurred. I think up/down clicks can just be ignored. ____________________________________________________________ Brent Easton Analyst/Programmer University of Western Sydney Email: [EMAIL PROTECTED] ------------------------ 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/
