Jeff Leslie
Member
And we all appreciate your efforts!
That explains why I have to close and restart VASSAL, not just VASL, to restore normal operation when the problem occurs.Our friends at VASSAL advise me that the problem is most likely caused by sending an incorrect html string to the code that parses it for display.
Scott Romanowski has given you the right way to get a counter list for an open scenario. Your use of the word "proper" concerns me. In no way are the names used in VASL correct, authoritative or even consistent. They are simply the names that VASL, built up over many years with counters created by many different people, uses. Use at your own risk. There is not at this point any joint integration between VASL and ASL Scenario Archive (which is an excellent site).I do not use VASL, I know (groan.) But I do enter scenarios on the ASL Scenario Archive.
My question is: Is there a way to get a list or files of the Armor/Gun counter names that VASL uses to properly insert these names into the Archive?
I will test for that on my system but have not seen it before. What I did find just yesterday is that if I was moving some labels that contained html code (often used to add info to a scenario in the area around the map), when I moved the label its contents were also pasted to the chat window - a similar issue to yours. Anybody else seen that?I have absolutely no clue if this is related but I found that using the scroll wheel on my Logitech mouse would generate unknown those characters in the chat window when it was active. I use separate windows for map, chat and server status.
Yes, I get the same thing.I will test for that on my system but have not seen it before. What I did find just yesterday is that if I was moving some labels that contained html code (often used to add info to a scenario in the area around the map), when I moved the label its contents were also pasted to the chat window - a similar issue to yours. Anybody else seen that?
Yes, I have seen that behaviour for a long time, but I can't say how long.I will test for that on my system but have not seen it before. What I did find just yesterday is that if I was moving some labels that contained html code (often used to add info to a scenario in the area around the map), when I moved the label its contents were also pasted to the chat window - a similar issue to yours. Anybody else seen that?
I think I have fixed the "moving a label counter" issue.Yes, I have seen that behaviour for a long time, but I can't say how long.
Right now I can't force it to happen with my mouse but I am forcing it to happen with my (yes) Logitech headset scroll wheel for the volume. I suspect it must be some sort of bleed-through from Logitech G Hub software.I think I have fixed the "moving a label counter" issue.
@PresterJohn I have not been able to replicate the problem with mouse-wheel-scrolling-putting-characters-into-chat. If you have a .vsav file where that happened, could you send it to me. If not, next time it happens, please do so.
I have spent more time than I can afford looking for this bug. The VASSAL folks are pretty certain it is an html parsing error. I agree with them but I can't find it.The one that still remains involves the delay in displaying user messages entered into the chat text box. Enter a message, it doesn't show. Enter a second message (or just hit enter a second time and the first message is pushed to Chat along with the second one. I can only trigger that error if (1) the Show Dice Stats after Dice Rolls preference is checked and (2) one of the three dr buttons has been clicked. I have not yet determined what is blocking the first message from being displayed. Any further testing and confirmation of results would be appreciated.
VASSAL uses several symbols as part of its management of chat messages, such as *, <, >, and ~. Using these at the start and end of messages is likely prone to error. Given the "delayed" messages bug, which remains unfound and unresolved, I am disinclined to be making any further changes at this time.Another bug I noticed today. I went to type "<virtual handshake>" at the start of a PBEM game, and found that nothing in angle brackets appears. If you type "This is <not> a test" ENTER, you see "This is a test". Methinks your HTML parsing may be a little too aggressive. Perhaps you need to sanitize your user input. :-D https://xkcd.com/327/
My advice is 6.6.6/3.6.19.What is the current pairing of VASSAL/ VASL that works best.
I might be able to assist here, but I need to know how to reproduce the problem.VASSAL uses several symbols as part of its management of chat messages, such as *, <, >, and ~. Using these at the start and end of messages is likely prone to error. Given the "delayed" messages bug, which remains unfound and unresolved, I am disinclined to be making any further changes at this time.
Your expertise would be much appreciated.I might be able to assist here, but I need to know how to reproduce the problem.
What makes him think that?Secondly, I believe from Scott's message that <handshake> in a html environment should produce the handshake emoji.