I have not made any effort
to maintain Windows XP (or 2000!) support in a long time. In fact, I recently changed the alpha project configuration so that it no longer prefers VS2010 for 32-bit builds, since newer compilers support more modern C++ language features. I think this might break Windows 2000 support, actually, but I didn't care to test it.
I wrote a little about it in the project readme:
AutoHotkey supports Windows XP with or without service packs and Windows 2000 via an asm patch (win2kcompat.asm). Support may be removed if maintaining it becomes non-trivial. Older versions are not supported.
Source: Lexikos/AutoHotkey_L at alpha
Aside from SoundGet/SoundSet, which I intend to review before v2.0, I do not think there is much specific to Windows XP that would affect code size visibly. The only other thing I can think of at the moment is owner-drawn menu icons, which are used only on 2k/XP but can be removed without affecting functionality much.
Flipeador wrote:The reason is simple, they could stop working
That's unlikely. Haven't you seen 20-30 year old Windows 3.1 file dialogs used in modern programs? I have.
(or malfunction) on any Windows update
I have every confidence in Microsoft's ability to make old and new
things malfunction via Windows update.
No one currently programming a "modern" application will bother giving support for Windows XP
I am sometimes required to deal with Windows XP and Vista computers at work, and
I use modern software which supports Windows XP. Although I honestly don't use AutoHotkey much at work, the ability to run AutoHotkey v2 on a Windows XP computer might be directly useful to me. If I have a v2 script and want to use it on XP, I'm not going to want to rewrite the script for v1, especially while at work.
However, I have no problem whatsoever with reduced
functionality on Windows XP.
I'm talking about FileSelect ... they provide limited functionality.
What are the new capabilities?
I propose to add a FileSave function
What's the difference between FileSave and FileSelect other than default options?
I would like to add here the functions marked to be removed in the documentation
What is the purpose in combining multiple distinct topics in this manner? You don't think they're worth a separate topic, or worth discussing
? You want the discussion to branch in multiple directions and be harder to follow? For one of your other topics
, this stopped me from marking an issue as solved, because you combined it with a bunch of unrelated things. Now if I review the topic, I need to skim through things that no longer matter.