IDE: Every time I enter ¡ the | goes to the end of the line
IDE: Every time I enter ¡ the | goes to the end of the line
When I try to enter a ¡ or ¿ using Alt+0161/Alt+0191 the cursor goes to the end of the line! Quite annoying.
Re: IDE: Every time I enter ¡ the | goes to the end of the l
> When I try to enter a ¡ or ¿ using Alt+0161/Alt+0191 the cursor goes to the end of the line
For what it's worth: I can't reproduce that here.
For what it's worth: I can't reproduce that here.
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
"PureBasic won't be object oriented, period" - Fred.
> This does not happen with NumLock enabled
I was trying with NumLock on, yes, which is why it worked for me.
To quote the help file for "Character Map" (bold emphasis is mine):
[...] open the document and position the insertion point where you want the
special character to appear. Then, with NUM LOCK on, hold down the ALT
key while using the number pad keys to type the Unicode character value.
So there you have it. Without NumLock on you can't type ALT+0161 etc.
I was trying with NumLock on, yes, which is why it worked for me.
To quote the help file for "Character Map" (bold emphasis is mine):
[...] open the document and position the insertion point where you want the
special character to appear. Then, with NUM LOCK on, hold down the ALT
key while using the number pad keys to type the Unicode character value.
So there you have it. Without NumLock on you can't type ALT+0161 etc.
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
"PureBasic won't be object oriented, period" - Fred.
FWIW, every so often over the last couple of days my CAPSLOCK key has reversed itself. Suddenly I was typing in caps. When tapping the CAPSLOCK key the CAPSLOCK light went on and everything acted as though it hadn't (lowercase default). It just toggled itself. Tapping the key again turned off the light and turned on the caps.
A reboot sorts it.
This appears to have started since the last auto-update for windows on XP-pro. At least that is the only thing I can think of that may have an impact, outside of some spec of dust or something inside the keyboard itself.
No NUMLOCK issues here, but maybe something similar?
A reboot sorts it.
This appears to have started since the last auto-update for windows on XP-pro. At least that is the only thing I can think of that may have an impact, outside of some spec of dust or something inside the keyboard itself.
No NUMLOCK issues here, but maybe something similar?
Dare2 cut down to size