Jon

Extended Length Support in File Functions (Beta) - For Reference

6 posts in this topic

Extended Path Checked (should have worked ok in 3.3.12.0)
=========================================================
DirCreate
DirGetSize
FileExists
FileFindFirstFile
FileFindNextFile
FileFlush
FileGetAttrib
FileGetEncoding
FileGetLongName
FileGetPos
FileGetSize
FileGetShortName
FileGetTime
FileGetVersion
FileRead
FileReadLine
FileReadToArray
FileSetPos
FileWrite
FileWriteLine


Extended Path Fixed in 3.3.13.1+ (Didn't work correctly in 3.3.12.0)
====================================================================
FileCopy
FileDelete
FileMove
FileOpen (when used with DirCreate flag)





Extended Path Rewrite Needed
============================
DirCopy (shell32)
DirMove (shell32)
DirRemove (shell32)

FileSetAttrib
FileSetTime
FileCreateNTFSLink

FileInstall


IniDelete
IniRead
IniReadSection
IniReadSectionNames
IniRenameSection
IniWrite
IniWriteSection


Extended Path Incompatible (Underlying API does not support) - Some may be possible to rewrite 
==============================================================================================
FileChangeDir
 (no function exists that can set directory with long paths)

FileCreateShortcut (shell32)

FileGetShortcut
 (shell32)
FileOpenDialog
 (shell32)
FileRecycle (shell32)

FileRecycleEmpty
 (shell32)
FileSaveDialog
 (shell32)
FileSelectFolder 

(shell32)

2 people like this

Share this post


Link to post
Share on other sites



Do you need a C library for ini functions? Would it help if it was written using the old plugin headers and AutoIt types from that?

Share this post


Link to post
Share on other sites

hmm... if there are extended length support in file functions to come - is some dedicated function to validate normal/extended length path/filepath planned?

Share this post


Link to post
Share on other sites

tested with latest beta 3.3.13.16 - tested DirCreate() found it is working, but it requires the calling script to add the unicode prefix.

tested DirRemove - it works only if i do NOT add the unicode prefix (if i add it, DirRemove fails).

adding the unicode prefix selectively to existing scripts would be a considerable headache.

any chance of making all relevant File* and Dir* functions add the unicode prefix internally?

Share this post


Link to post
Share on other sites

#6 ·  Posted

Some dedicated function to validate normal/extended length path/filepath planned?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now