Hi Ethan, There will be several enhancements to the LOS tool in version 3.0 of VASSAL. I am still working on it, but here is a summary of what I plan to include:
1. LOS Reporting - You can add a Report Format that will be executed whenever the mouse is released. Extra $...$ variables tyat can be used are: $FromLocation$ - Location thread was drawn from $ToLocation$ - Last Location thread was drawn to when mouse released $ToLocationList$ - A list of all ToLocations that the thread end passed through $CheckCount$ - A count of all ToLocations that the thread passed through $Range$ - The range from FromLocation to ToLocation You will be able to generate messages like <Brent> Check LOS from 0405 to 0706 (Range 3) [4 Locations check: 0505,0606,0605,0706] 2. Persistence - A LOS thread can be made to persist after the LOS operation is completed. Options will be Never, Always, Ctrl-Click&Drag. A Persisting LOS stays visibly on the screen after the LOS session is complete, until you click on the LOS button again. An alternate Icon is displayed while the LOS is persisting. If the LOS is both Persisting and Global, then both players can turn off their own display of the Persisting LOS. 3. Global Display - You will be able to choose whether your opponent can see the LOS thread. Options will be Never, Always, When Persisting. When Global Display is enabled and you release the mouse, the LOS will be echoed and displayed on your opponents screen. Your opponent will not see the Thread move through all locations and will not have his counters hidden. The default for all modules will be set to ReportFormat = Not sure??? Persistence = Ctrl-Click&Drag Global Display = When Persisting This will add the new features to the all modules by ctrl-click & Drag the LOS, but will leave normal operation unchanged. I am not sure whether we should add a default Report Format and start all modules reporting LOS checks or leave it blank and silent as now. Thoughts? Regards, Brent. >*********** REPLY SEPARATOR *********** > >On 23/02/2007 at 6:40 PM Ethan McKinney wrote: >So, to sum up, there's no way for Rob to do this, right? > >I want to add LOS snapping to the Screaming Eagles and Bloody Ridge >modules, but I've been baffled as to how to accomplish it. I just >joined this group because of this question, and I see right away that >Brent is working on making it a standard part of VASSAL! Bravo! > >Work faster, Brent, work faster... > >Yours, > >Ethan McKinney > >--- In [email protected], "Brent Easton" <[EMAIL PROTECTED]> wrote: >> >> Hi Rob, >> >> There is an enhancement request in already to add start/end point >snapping to the standard VASSAL LOS thread. There will shortly be a >poll where you will be able to vote for your favourite enhancements. >> >> The VASL/VSQL LOS tools will not work in your module as they depend >on a whole lot of underlying structure in other parts of the VASL/VSQL >code base. >> >> There is no need to search for stuff on codase, all of the source >you need (including LOS_thread.java) is available from the SVN >repository on Sourceforge. Detailed instructions are available in the >Developers Corner section of the documentation on www.vassalengine.com. >> >> Regards, >> Brent. >> >> *********** REPLY SEPARATOR *********** >> >> On 11/12/2006 at 4:18 AM Rob Doane wrote: >> I hope someone out there is willing to help a real neophyte. I am >> creating my first VASSAL module and I would like to add the LOS tool >> found in VASL and VSQL that snaps to the grid. My problem: I know >> absolutely nothing about programming or Java. I have found the >> "LOS_Thread.java" file at www.codase.com >> that Rodney Kinney wrote, and it seems this is the tool I need. I >> downloaded Eclipse and tried to create a project and class, but it >> didn't work. Unfortunately I just haven't been able to figure it out >> from the tutorials and the help. Can somebody walk me through exactly >> what I'm supposed to do with this code after I open Eclipse? If you >> can, I will be forever grateful! >> >> Thanks, >> Rob Doane > > > ____________________________________________________________ Brent Easton Analyst/Programmer University of Western Sydney Email: [EMAIL PROTECTED]
