Search found 9394 matches

by lexikos
23 Mar 2024, 20:32
Forum: Bug Reports
Topic: [V 1.1] Object.Delete(Key) doesn't work in some cases Topic is solved
Replies: 1
Views: 101

Re: [V 1.1] Object.Delete(Key) doesn't work in some cases Topic is solved

This is by design. words.Delete(NewWord) will try to call the function named "2". One of many design flaws of v1 fixed by v2. (You are effectively doing the same as words.Delete := 2 , which would also prevent the method from being called in v2. But in v2, an error would be thrown.) Also, I see you ...
by lexikos
23 Mar 2024, 06:13
Forum: Bug Reports
Topic: CaretGetPos wrong coordinates
Replies: 5
Views: 467

Re: CaretGetPos wrong coordinates

Last time I read it, the remarks for GetDpiForWindow didn't seem to fully explain how the value is determined. I think I had a cognitive disconnect between "The system DPI" and what it actually means on Windows 10: the baseline DPI for the target process . On Windows 8.1, I think the system DPI is t...
by lexikos
23 Mar 2024, 05:47
Forum: Scripts and Functions (v1)
Topic: TreeList Control (Experimental)
Replies: 21
Views: 6880

Re: TreeList Control (Experimental)

The reason, apparently, is that TreeList is not registered with CS_GLOBALCLASS. I happened to come across this at some point, and made a note to look into this limitation. At first glance, it would seem that the Custom control needs a way to specify the module. However, it is quite trivial to work ...
by lexikos
23 Mar 2024, 01:50
Forum: Bug Reports
Topic: CaretGetPos wrong coordinates
Replies: 5
Views: 467

Re: CaretGetPos wrong coordinates

Am I missing something, or are the GetWindowDpiAwarenessContext and GetAwarenessFromDpiAwarenessContext calls unnecessary? Can someone confirm that the issue with CaretGetPos exists on Windows >=8.1 <1607? If so, I'm not expecting there to be a fix for those versions. GetDpiForMonitor (like per-moni...
by lexikos
23 Mar 2024, 01:09
Forum: Bug Reports
Topic: Remapping Alt key is unreliable
Replies: 10
Views: 1184

Re: Remapping Alt key is unreliable

This might have been fixed by v2.0.12.
Fixed Send erroneously releasing a modifier due to a race condition. For example, ~LAlt::Send "{Blind}x" intermittently released LAlt if some other keyboard hook was installed more recently than the script's own hook.
by lexikos
22 Mar 2024, 23:06
Forum: Scripts and Functions (v2)
Topic: Apply hotkeys to the new context menu on Windows 11
Replies: 9
Views: 3528

Re: Apply hotkeys to the new context menu on Windows 11

At some point Microsoft changed the window class of the context menu from Xaml_WindowedPopupClass to Microsoft.UI.Content.PopupWindowSiteBridge. Aside from that, the script still works.
by lexikos
22 Mar 2024, 20:28
Forum: Bug Reports
Topic: " Up::" seems to not work properly in 2.0.7 Topic is solved
Replies: 3
Views: 744

Re: " Up::" seems to not work properly in 2.0.7 Topic is solved

I previously suggested that SendEvent could be a workaround, but that was a mistake. When SendEvent is used, or when Send or SendInput falls back to SendEvent mode, the issue you described is present even on v2.0.6 and earlier. SendInput mode was not affected by the issue because of the bug I mentio...
by lexikos
22 Mar 2024, 20:22
Forum: Bug Reports
Topic: SysGetIPAddresses() causes Invalid memory read/write. Topic is solved
Replies: 7
Views: 245

Re: SysGetIPAddresses() causes Invalid memory read/write. Topic is solved

A_IPAddressX and SysGetIPAddresses weren't designed to handle failure. v2.0.12 fixes this. However, whatever condition was causing it to fail will likely still do so; you'll just get an empty array instead of a Critical Error. If you are not having issues in other software, I would suggest looking a...
by lexikos
22 Mar 2024, 20:15
Forum: Bug Reports
Topic: not work when !]:: Send("^{Insert}a") Topic is solved
Replies: 8
Views: 326

Re: not work when !]:: Send("^{Insert}a") Topic is solved

Fixed by v2.0.12.

@ZhuangQu it would have been helpful to say that when mcl first brought up AltGr.
by lexikos
22 Mar 2024, 20:15
Forum: Bug Reports
Topic: [2.0.11] Error during Setup // "Error: (87) Falscher Parameter." Topic is solved
Replies: 4
Views: 227

Re: [2.0.11] Error during Setup // "Error: (87) Falscher Parameter." Topic is solved

Although it won't be needed for another 4 years... this is fixed by v2.0.12.
by lexikos
22 Mar 2024, 20:12
Forum: Bug Reports
Topic: Obscure GUI Picture-related bug Topic is solved
Replies: 7
Views: 2080

Re: Obscure GUI Picture-related bug Topic is solved

It appears to be the case that LoadImage and CopyImage are unable to resize a monochrome icon. It doesn't seem worth coming up with another way to resize the icon, just to allow monochrome icons to scale. The resizing issue is avoided for icon 115 in v2.0.12, as it no longer selects the monochrome i...
by lexikos
22 Mar 2024, 20:08
Forum: Bug Reports
Topic: [V2.0.11:] An inconsistence in "static method" Topic is solved
Replies: 5
Views: 366

Re: [V2.0.11:] An inconsistence in "static method" Topic is solved

The documentation error has been fixed in v2.0.12.
by lexikos
22 Mar 2024, 20:02
Forum: Bug Reports
Topic: AutoHotKey v2.0.11 has a PCRE execution error Topic is solved
Replies: 3
Views: 438

Re: AutoHotKey v2.0.11 has a PCRE execution error Topic is solved

v2.0.12 fixes this, and/or at least handles PCRE execution errors better.
by lexikos
22 Mar 2024, 20:00
Forum: Bug Reports
Topic: Generated key up for unknown reason, and missed key presses Topic is solved
Replies: 1
Views: 130

Re: Generated key up for unknown reason, and missed key presses Topic is solved

This should be fixed by v2.0.12.
Fixed Send erroneously releasing a modifier due to a race condition. For example, ~LAlt::Send "{Blind}x" intermittently released LAlt if some other keyboard hook was installed more recently than the script's own hook.
by lexikos
22 Mar 2024, 19:54
Forum: Bug Reports
Topic: CaretGetPos wrong coordinates
Replies: 5
Views: 467

Re: CaretGetPos wrong coordinates

I did a bunch of testing, but I forget the details as it was several months ago. There are some configurations which aren't covered by your workaround. IIRC, it is when there are two screens with different scaling settings, both greater than 100%. I didn't find a feasible way to detect or calculate ...

Go to advanced search