Invalid_Name for all XML created with CL3

[jasondavis]

All my data files show this Invalid_Name in the saved XML on Window 10

<?xml version="1.0" encoding="UTF-8"?>
<ClipChainData>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
</ClipChainData>

[hi5]

Strange

• The above is the XML for the ClipChain, when you manually add an entry and close the clipchain (via the "close clipchain" button - is saves the XML upon closing the Gui (not when hiding it with Ctrl+Win+F11 I think)) is it still empty?
• Is the History also empty (clipdata\history\History.xml)?

[jasondavis]

@hi5 Thanks for the reply....

1. All my XML files in the ClipData folders have this type of data:

<?xml version="1.0" encoding="UTF-8"?>
<ClipChainData>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
	<Invalid_Name id="" ahk="True"></Invalid_Name>
</ClipChainData>

2. Yes the History.xml file is in the above format as well.

---

Besides the issues with XML data everything else works great.

Perhaps it is some sort of encoding issue i'm not sure why though.

On another note I am looking to modify the ClipChain code to allow a HotKey to add/insert selected text to the clipchain so I can open the ClipChain GUI and then copy new items to the chain without having to always use the Insert GUI.

Is this a feature you would be interested in as well?

Thanks

[hi5]

I've been running the Unicode version of AutoHotkey for so long I keep forgetting there is an Ansi version - XA only works correctly with AutoHotkeyU64.exe or AutoHotkeyU32.exe which you can find in your AutoHotkey folder (if you've installed it, otherwise you'll find them in the ZIP file you can download from the AutoHotkey website).
If you just want to quickly test it: close any copies of CL3 you have running and start copy one of those Unicode versions to the CL3 folder as cl3.exe and start it. It will launch cl3.ahk automatically. Now it should work.

I'd not only recommend the Unicode version of AutoHotkey in general, but especially for CL3 so it can properly handle unicode text (non-English languages, Unicode characters incl. emoji).

I should add a note to the CL3 readme about it as well.

Reference: hi5/XA#1 (comment)

Edit: try upgrading AutoHotkey, it should actually work with Ansi as one my other scripts relied on it at first and XA worked fine at the time now that I think about it. (That script now works with Unicode & Ansi (F4MiniMenu))

[hi5]

I've used XA on Win7/8/10 without any issues or installing something but apart for checking with newer updates of AHK, you could try and see if you actually have the msxml6.dll which is I think a requirement for the ComObjCreate("MSXML2.DOMdocument.6.0") XA uses.

A search for msxml*.dll in

 c:\Windows\System32\
 c:\Windows\SysWOW64\

should show msxml6.dll

❓