Character lost

[SFiedler]

Hi,

I am running VASL on a Mac and the latest VASL version has a minor but somewhat annoying bug(?). After using VASL interface (clicking the dice etc) the first character types is always missing unless one first click the chat window. Have anyone else noticed this and do you have a smart workaround? It is a little annoying to write AP TH when it comes out as P TH.

Otherwise VASL is just great!

 

[asloser]

I have noticed this as well.

 

[hongkongwargamer]

Thanks for bringing it up. It's been so long that I automatically type the first character twice for every line when I do PBeM logs!

 

[Pacman Ghost]

After using VASL interface (clicking the dice etc) the first character types is always missing unless one first click the chat window.

It's not just the chat window. I try to use the keyboard as much as possible, in particular, for rolling dice, and more often than not, the first attempt will get missed, even when the main window has focus.

 

[DougRim]

Are you all using Macs and the latest VASL? Which VASSAL versions?

I use Windows and I have not noticed this at all. Playing with a guy who likes his log files so we are often adding info via chat.

 

[asloser]

Windows, VASSAL 3.4.6, VASL 6.6.1

 

[Pacman Ghost]

Are you all using Macs and the latest VASL? Which VASSAL versions?

Windows 10 + VASSAL 3.5.1 + VASL 6.6.1

I just tried now and it seemed quite responsive, so I'm wondering if it's maybe just an issue when playing with someone remotely.

 

[sushidog]

I've been getting this for a while now, not just with VASL but with VASSAL for other games. All PBEM, so all related to typing into the log line.

Win10 VASSAL 3.5.0

 

[hongkongwargamer]

Mac VASSAL 3.5.1 VASL 6.6.1

 

[atomic]

MacOS BigSur (11.2.1)
VASSAL 3.4.6
VASL 6.6.1

 

[DougRim]

After rereading the OP, I was able to replicate the problem. I didn't realize that people were typing comments into the chat window without selecting the chat line first. It would never have occurred to me that you could/would do such a thing. I don't understand why it even works at all, especially since keyboard commands are such an important feature of vassal. How it knows what is a command and what is a comment is completely beyond me. Magic!

Anyway, I can get the first character to miss in certain situations, even when not online. Given Sushidog's comments, I am inclined to think this is a VASSAL problem. I will raise it with them.

The workaround in the short term, as you know, is to ensure the chat text box has the focus. that is a PITA for everyone but me who was doing that anyway! LOL.

 

[BigAl737]

I’d bet this started happening when VASSAL introduced word commands without a linked system key.

 

[sushidog]

After rereading the OP, I was able to replicate the problem. I didn't realize that people were typing comments into the chat window without selecting the chat line first. It would never have occurred to me that you could/would do such a thing. I don't understand why it even works at all, especially since keyboard commands are such an important feature of vassal. How it knows what is a command and what is a comment is completely beyond me. Magic!

Anyway, I can get the first character to miss in certain situations, even when not online. Given Sushidog's comments, I am inclined to think this is a VASSAL problem. I will raise it with them.

The workaround in the short term, as you know, is to ensure the chat text box has the focus. that is a PITA for everyone but me who was doing that anyway! LOL.

Yes, it always worked great. The only time there was a problem is if you accidentally hit a ctrl+ hot key combo that was active in whatever module you were using. Most modules don't use simple shift+ commands, so it's not a big deal. I pbem a lot of different wargames; we type constantly as we move/fire/etc. It's a giant PITA when you have to click in the chat line to activate it. Luckily, that's not generally the case. This little bug just makes you often have to hit the first character twice to get it to register. (Some modules, like Command and Colors Nappy, have a separate dice tray pop up tray. When you roll the dice there and then try to type your response, the chat line is no longer active, you have to either click on the main screen or the chat line. So I think it's only active if the main screen is active.)

 

[Pacman Ghost]

I just tried now and it seemed quite responsive, so I'm wondering if it's maybe just an issue when playing with someone remotely.

Had another 2 sessions with someone online, and VASSAL was still losing key-presses in the main map window. I mentioned it to my opponent, and he said he's been seeing the same thing (Fedora + VASSAL 3.5.1 + VASL 6.6.1), but seemed to think it might have something to do with having a piece selected. Maybe it's a counter that's consuming the event...?

Actually, I did a quick test offline, and it seems that this might be it. A F2 die roll is often ignored if a counter is selected, but seems to be accepted every time otherwise.

 

[hongkongwargamer]

After rereading the OP, I was able to replicate the problem. I didn't realize that people were typing comments into the chat window without selecting the chat line first. It would never have occurred to me that you could/would do such a thing. I don't understand why it even works at all, especially since keyboard commands are such an important feature of vassal. How it knows what is a command and what is a comment is completely beyond me. Magic!

Anyway, I can get the first character to miss in certain situations, even when not online. Given Sushidog's comments, I am inclined to think this is a VASSAL problem. I will raise it with them.

The workaround in the short term, as you know, is to ensure the chat text box has the focus. that is a PITA for everyone but me who was doing that anyway! LOL.

PBeM

 

[uckelman]

Noted as Bug 14143. Try VASSAL 3.5.4-SNAPSHOT-7251fec33. Does that solve the problem for you?

 

[hongkongwargamer]

Noted as Bug 14143. Try VASSAL 3.5.4-SNAPSHOT-7251fec33. Does that solve the problem for you?

I think it does. I just did a log just like the good old days. Thanks!!

 

[DougRim]

I will wait until VASSAL3.5.4 is officially released and then build VASL6.6.2 with it so that we incorporate this bug fix.