Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.8.1, 6.9.0 Beta1
-
None
-
2
Description
The problem with QTemporaryFile's scanning for XXXXXX is when the pattern already includes such an instance. Yes, you can safely (after QTBUG-132597) assume that it will always replace the last one, so you can append .XXXXXX and it will always do the correct thing, but if a user relies on the "if the file name doesn't contain XXXXXX, appends it" behaviour of the constructor, then if the filename does contain XXXXXX, it might be replaced at an unexpected place. A version that doesn't scan would also ... well, not have to scan, saving time.
Attachments
Issue Links
- clones
-
QTBUG-132646 Add a variant of QTemporaryFile::rename() that overwrites
-
- In Review
-
- relates to
-
QTBUG-132590 Unclear relation between QTemporaryFile::{autoRemove,rename}()
-
- Reported
-