Opened 15 years ago
Closed 11 years ago
#1120 closed Feature Request (Rejected)
Overwrite hidden system files with FileInstall()
Reported by: | partypooper@… | Owned by: | Valik |
---|---|---|---|
Milestone: | Component: | AutoIt | |
Version: | Severity: | None | |
Keywords: | FileInstall | Cc: |
Description
FileInstall should to be able to overwrite files with +HS attributes without having to check for and reassign the attributes, first. Currently, it fails to do this even if you select the overwrite flag.
Attachments (0)
Change History (10)
comment:1 Changed 15 years ago by TicketCleanup
- Version 3.3.1.1 deleted
comment:2 Changed 15 years ago by Jpm
Fileinstall is design to install user files. For me that means normal file.
If the user when something more complicated it is up to his script to take care.
For me such feature will not be accepted.
comment:3 Changed 15 years ago by Valik
- Resolution set to Rejected
- Status changed from new to closed
I agree.
comment:4 Changed 15 years ago by partypooper@…
User files can be system and/or hidden, not just archive and read-only. I was just thinking that since the other File...() commands all work with +HS so why not FileInstall(). No biggy, it's a simple matter to delete the file first before using fileinstall and then changing the attributes to +HS.
As a compromise, can we get a footnote added to the FileInstall section of the help file that the overwrite function doesn't work for +HS attributed files then.
comment:5 follow-up: ↓ 6 Changed 15 years ago by Jpm
Filecopy does not work either
I will add the same remarks
comment:6 in reply to: ↑ 5 Changed 15 years ago by Valik
- Resolution Rejected deleted
- Status changed from closed to reopened
Replying to Jpm:
Filecopy does not work either
I will add the same remarks
In that case, maybe we should reconsider. I can certainly copy SuperHidden files with stuff like Explorer. Given that the overwrite flag is being used, we should probably do the work for the user. It seems pointless to allow an overwrite flag but still make the user write additional code to ensure the overwrite happens.
The same goes for FileCopy() and FileMove() as well. Also DirCopy() and DirMove() need tested to ensure the overwrite flag always overwrites when it should.
comment:7 Changed 15 years ago by anonymous
Sorry, my mistake - I assumed because FileOpen() and FileMove() worked the others did too. First lesson I guess is not to assume anything. Thumbs.db is a good example of what I want overwritten when installing (re-installing) picture directories.
comment:8 Changed 15 years ago by partypooper@…
FYI, FileWriteLine() works but _FileWriteToLine() doesn't.
comment:9 Changed 15 years ago by Jpm
- Owner set to Valik
- Status changed from reopened to assigned
comment:10 Changed 11 years ago by Jon
- Resolution set to Rejected
- Status changed from assigned to closed
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
Automatic ticket cleanup.