alt+ascii codes problem with new virtual input system

zoom · Post by **zoom** » Mon May 15, 2006 11:29 am

Hi,

I hope I'posting in the right section

I had a few bugs with my mouse extra buttons after this weekend's patch so I switched to the new virtual input system for innerspace. This fixed the mouse problems but sorta created a new one.

I use an international keyboard and I often have to use alt+ascii codes when I write in french (typing alt+0233 gets a "é" for example). This no longer works under innerspace with the new virtual input system.

thx in advance

Post by **Lax** » Mon May 15, 2006 11:42 am

Right section, thanks

I understand the bit about the international keyboard, and I will do what I can to solve the problem asap, but I have a question about this.

I'm positive that in France the average person does not type alt+0233 to type a "é"... is it really necessary to use alt+unicode to type that with an international keyboard?

Also, about the mouse buttons with the old input system, is this ONLY with the non-left/right click buttons? I was trying to duplicate the problem described on ismods.com, but I didn't realize that you specifically said the extra ones, and the left/right click buttons worked fine.

Thanks for reporting the issues, I'll take care of them today

zoom · Post by **zoom** » Mon May 15, 2006 12:06 pm

On the keyboard thing, I rushed on a logitech g15 international keyboard because French version was'nt planned for mass production yet at the time I bought it. I actually bind a g15 key to alt+0233 in order to tpye "é". If you know another way than alt+code to type "é", i would be happy to learn it.

On the mouse thing, I'm using a logitech mx518

my config was the following:
virtual input off
win32 keyb on
win32 mouse on
directinput keyb on
directinput mouse on
hybrid mouse off
keystroke delay on
lock foreground off
background window mouse position actual

at launch, i believe left and right clicks were working fine.
more specificly,
pressing mouse button 4 (internet browser default back button) didnt seem to produce any effect at all
pressing mouse button 5 (internet browser forward button) worked from time to time and also locked mouselook as if the mouse button was'nt released.
pressing middle mouse button (click on the mouse wheel) didnt produce any effect at all

possibly left and right clicks didnt work after messing with mouse button 5

I hope that helps

Post by **Lax** » Mon May 15, 2006 12:55 pm

On the keyboard thing, I rushed on a logitech g15 international keyboard because French version was'nt planned for mass production yet at the time I bought it. I actually bind a g15 key to alt+0233 in order to tpye "é". If you know another way than alt+code to type "é", i would be happy to learn it.

I dont know another way, I'm a stupid American and I speak very little of any language other than English

Je suis desolee -- I don't know anymore if that's stated right and I certainly dont know how to do the accent aigu or grave or whichever it is (until you mention that it's alt+0233)

And with the G15 keyboard, I just picked one of those up to add support for the G buttons for IS binds to go along with the other new features. Pain in the butt since they dont support DirectInput for those keys (short sighted for them imho), but I'm working on that. If you like the key emulation behavior their software provides, that's fine and will still work too

The further information on the extra buttons helps, thank you.

Post by **Lax** » Mon May 15, 2006 1:25 pm

Ok, I found the problem with the additional mouse buttons with the old input system, and fixed it. This is patched into the current stable release if you have IS patch up.

Working on alt+unicode in Virtual Input now

Post by **Lax** » Mon May 15, 2006 2:39 pm

OK, build 3982 is up, and should solve the problems you were having with both the old system and the new system.

The Alt+Code sequences wont work in LavishGUI text editing elements still (e.g. to type é into a console wnidow), but that's for another day I suppose

Please continue to report any problems you experience

zoom · Post by **zoom** » Tue May 16, 2006 3:23 am

i confirm alt+ascii# works fine in the game and not in the is console.

some new detail came up with your last build:
numpad keys dont work as numbers anymore ingame, they work fine as associated hotkeys but they dont type out their #. (they work fine in the game console though, problem only appears ingame)

sorry for being such a pita, i just report stuff as i come upon it, dont bother fixing this on a hourly basis, it's nowhere near critical

Post by **Lax** » Tue May 16, 2006 9:38 am

No worries, I'm trying to get the Virtual Input system ready for completely replacing the older systems, and the earlier these bugs get reported the better. It would be hell if I destroyed the old systems and THEN people told me these things!

Besides, the input system is what I am actively working on right now, so it's better for me to fix all of this while it's all fresh in my head. It'll get fixed today

zoom · Post by **zoom** » Sat May 27, 2006 10:31 am

It'll get fixed today

Just a quick post to remind you Lax these artefacts of your Alt+ascii VI code are still bugged, especially :

Numpad # keys (0,1,2,.. 9) not producing their associated number ingame. It works as an associated hotkey, it doesnt work to type out chat text. It works in game console. +-/*and enter work fine.

Ingame ALT+UPARROW doesnt work (chat history in wow)

Post by **Lax** » Sat May 27, 2006 11:24 am

Thanks for the reminder. Build 4002 is now up with these issues fixed. Let me know if you find any other problems

zoom · Post by **zoom** » Sun May 28, 2006 3:21 am

Both issues fixed now, thank you Lax

zoom · Post by **zoom** » Mon Jan 29, 2007 6:02 am

quick bump to report release 4330 broke alt+ascii codes
(exemple alt+0233 on numpad doesnt produce ? as it should)

zoom · Post by **zoom** » Sat May 12, 2007 6:32 am

Sorry lax, another bump, I realise this problem doesnt impact many people but it's been 4 months or so and this issue hasn't been solved.

To summarize: ALT+ASCII# dont produce special charaters under innerspace.

History: a long time ago, it used to work. Then virtual input system broke it. Then you fixed it. Finally, release 4330 broke it again end january 2007.

Thanks in advance Lax