- Napoleon 2m Bad bish is bad.
- RealHumanBean 16s Something?
- wiebman 20m
- Hippo 12m
- jwimpeney 2m
- Ostheim 9m
- Atheran 4s
- Lycanthorph 9m
- Malanth 27s
- FancyPenguin 2m
- ZaCyril 2s https://youtu.be/9r4WD60uM18
- Neekly 2h
- Baguette 1h ye boi
- Rigo 27m
- Grey0 12m
- maxxieway26 3h
- Cromptonymous 22s
- SolBro 4h
- jsmith225 10h
- Rangerkrauser 10h
- Azelle 16h
a Cerberus 22h Head Builder & GM when I need to
- Chrissl1983 1h Really enjoying this awesome game to the fullest!
j Johnny 7h New Code Written Nightly. Not a GM.
And 25 more hiding and/or disguised
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

Web Client and the Down Arrow

I have grown to really enjoy the Web Client. It's pretty awesome. There is, however, this single, little thing that drives me crazy. It's largely my own fault but it has hit me often enough that I thought I'd write it down. Maybe it's affected others.

When I am typing in a command (like a long pose) and accidentally hit the down arrow on your keyboard, it is gone (as whatever you were typing disappears and can not be recovered). This happens to me sometimes because, after typing out the pose, I try and proofread it before sending. When I see a typo, I try and arrow back to fix it and all too often I fat finger it and hit the down arrow instead of or together with the left arrow. Then it is all gone.

Like I said, root cause is me hitting the wrong key. I know that but I still think it would be great if this didn't happen.

Of course, this might be something to do with the browser I use or my OS for all I know. I just know it get's me often enough to make be feel pain. I am not even sure if there is a reasonable change that would help this or if it's worth the effort.

I exclusively use the webclient and sometimes i feel a little disadvantaged, but its a -great- easy client i agree. I'm pretty sure this is just how it is with the down arrow, though. I've done it many times before, too, but i would really hate to lose the arrow functionality. Really, i'm pretty sure you just need to stop using the arrow keys for navigation within the text box. Just use your mousepad or whatever.

OR you can do what i sometimes do (if you don't already) and write out a pose/emote/spoof that i know should be proofread without the command symbol first. Hit enter. and then use those pesky arrows against themselves and hit the up arrow to bring the pose back up again from the beginning. you can just scroll through the pose then. I usually just do this to ready poses ahead of time and then edit as circumstances in the scene changes or to get pose ideas into the flow and readily accessible with a few punches of the up arrow. Start using them as a tool and maybe you "forget" they are for navigation too? :)

Hey there. I've encountered the same issue and, after a while, found a solution that worked for me.

Most computers have the means to restore/revert the last few inputs with a Ctrl based command. On my keyboard that command is Ctrl + Z. If and when I lose my input to the down command I just hit Ctrl + Z and, as if by magic, my missing text is back. Ctrl + Y restores text lost by excessive pressing of Ctrl + Z.

Hope this helps!

This also drives me a bit crazy. I updated the web client code to fix this issue by making it so when you hit down, it saves your previously entered text into the command buffer, so you don't lose it-- but you can still type a down arrow to get to a fresh input if you need it.

This is not live yet, as Johnny needs to review/approve the feature.

Feature approved, should be live next time we roll out webclient updates.

All I can say is that it feels like Christmas. I mean, it's far from essential and I'm probably one of very few who actually cares but it happened. Thank's Slither Claus!


This change is now live (as of last night). You might need to clear your cache to pick up the changes, you might not.

I noticed a small bug with this new update...

If you double-click the black screen to disable the auto-scroll and you try to scroll up with the arrow keys, it will focus the caret on the text box. The buffer won't scroll up, it will just select the previously entered text. It's a bit annoying, can you make it so it doesn't select the previously entered text if the text box is empty and the scroll is paused?

What you're describing is the way I made it on purpose. I'm thinking of ways to make this more usable for folks like you that want the focus to be on the text area when the scroll is paused.

Maybe making it so when it pauses it puts the focus on the text area and when you unpause it returns it to the text box...

Also, FYI: command + period (might be control on PC?) will pause/resume the scroll.

I actually like that the text box stays in focus now after a double-click to the text area.

Okay, there is an update that I've made, that will go out when we next roll out a change. Double clicking will keep the focus on the text area so you can scroll. If you want your focus to remain in the input box, you can use the command + . shortcut.

It makes sense to allow scrolling right away on pause. It makes sense to return it to the input box.