AutoHotkey Community

It is currently May 21st, 2012, 5:21 pm

All times are UTC [ DST ]


Search found 37 matches
Search these results:

Author Message

 Forum: Support   Topic: How to get NumpadSub to work?

Posted: December 12th, 2011, 3:56 pm 

Replies: 1
Views: 105


I don't get this code to work:

:?c*:NumpadSub#::−

What I try is to get a "real minus" (−) instead of a minus/hyphen.

Where is the mistake?

 Forum: Support   Topic: escape don't work?

 Post subject: escape don't work?
Posted: December 11th, 2011, 11:22 am 

Replies: 1
Views: 68


Does someone have a working solution?
Somehow the escape sequence doesn't work:

:?c*: >#::{^}

:?c*: \#::``

:?c*: '#::´

I want to get a ^ ` and ´ as output.

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: June 12th, 2010, 11:35 pm 

Replies: 551
Views: 102257


keyboard ID = 67568647

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: June 12th, 2010, 11:29 pm 

Replies: 551
Views: 102257


I found some information here:
* http://social.msdn.microsoft.com/Forums ... c7ccea735c
* http://blogs.msdn.com/b/michkap/archive ... 48775.aspx
Apparently ToUnicode[Ex] can undesiredly erase the keyboard buffer.
Hope that helps.

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: June 12th, 2010, 11:14 pm 

Replies: 551
Views: 102257


I am using German keyboard layout (with nightly build 6e9259), deadkey problems are still the same.
It looks as if the keyboard buffer gets erased, so the following input does not trigger the execution of the deadkey.

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: June 11th, 2010, 7:33 pm 

Replies: 551
Views: 102257


I am now using nightly build IronAHK-d73a2d (= the most recent I think) but the deadkey problem persists, only in a weirder way: ^^ will give ^^ (correct) ^k will just give k (instead of ^k) ^e will just give e (instead of ê) Typing e while holding ^ down will give ê, but only if a non-modified char...

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: May 31st, 2010, 10:18 pm 

Replies: 551
Views: 102257


Thanks! Now AltGr works! :D

Just one tiny thing... I realised that the deadkeys ´ ` ^ don't work properly while a script is running. E.g. instead of café and même, I get caf´´e and m^^eme.

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: May 30th, 2010, 11:06 pm 

Replies: 551
Views: 102257


Thank you very much! :D I used IronAHK-6f3f20 now and case sensitivity works fine, both for lowercase/uppercase mix and for {SHIFTUP}/{SHIFTDOWN}. The only remaining problem is that I still cannot use AltGr characters (on my keyboard layout \ and ~) in Hotstrings. Hotstrings with ~ don't execute at ...

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: May 30th, 2010, 3:02 am 

Replies: 551
Views: 102257


Sorry to revert again to the case sensitivity issue... but for me, Hotstrings still only work in uppercase (build IronAHK-77257a, German kbd layout). Actually not even that: {SHIFTDOWN}a/{SHIFTUP} will trigger a Hotstring but {SHIFTDOWN}a{SHIFTUP}{SHIFTDO...

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: May 24th, 2010, 10:26 pm 

Replies: 551
Views: 102257


Where can I get the latest nightly build? I tried with 131922 and b0be3e but the string recognition still won't work:

Code:
:?c*:A:#::Ä
will work but

Code:
:?c* :a:#::ä
will not.

Also, xß# and x\# (no hotstrings in my script) will result in x being deleted.

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: May 22nd, 2010, 8:57 pm 

Replies: 551
Views: 102257


I think my last post was rubbish because I realised that AutoScriptWriter reads English layout from a German keyboard even when I have no IronAHK script running. So the problem really seems to be case sensitivity for non-characters: :?c*:S/#::$ (same case) will work :?c*:c/#::¢ (case change) will no...

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: May 20th, 2010, 11:13 pm 

Replies: 551
Views: 102257


Keyboard layout is probably the key :wink:
I have a German keyboard layout installed, but when I record
Quote:
äöü

with AutoScriptWriter, I see
Quote:
'`;

Did you somehow put UK keyboard layout as default? How can I override it?

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: May 19th, 2010, 10:27 pm 

Replies: 551
Views: 102257


Yes, I tried with both encodings. Interestingly, :?c*:c7#::¢ will work. It looks as if when non-letter characters are used in a hotstring, the case sensitivity works only if the first two characters of the hotstring are in the same case, i.e. S/ or c7 but not c/. Any explanation?

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: May 19th, 2010, 9:42 pm 

Replies: 551
Views: 102257


I now tried with IronAHK-131922.

Code:
:?c*:c/#::¢


did not work. Neither did

Code:
:c* :1/4 ::¼


(I use WinXP.)

 Forum: Custom   Topic: IronAHK (alpha): cross platform .NET rewrite of AutoHotkey

Posted: May 19th, 2010, 8:55 pm 

Replies: 551
Views: 102257


I encountered something strange:

Code:
:?c*:S/#::$


will give $ but

Code:
:?c*:c/#::¢


will not give ¢.

Could it be a Unicode mapping problem because $ is ASCII and ¢ is ANSI/Latin-1?
I am using IronAHK-33f345.
Sort by:  
Page 1 of 3 [ Search found 37 matches ]


All times are UTC [ DST ]


Powered by phpBB® Forum Software © phpBB Group