shift+f4 does not check if the file to edit has been created

[sz]

in a dir where i dont have write rights, shift+f4 does not create the file, but it starts the external editor (which complains that file does not exists or won't be able to save the file, depending on its own implementation, but that is not a tcmd issue), maybe tcmd should issue a warning in this case
(i don't think that asking for admin rights in this case can be a good solution, because the external editor still may be able to save the file or create .bak files)

(7.0pb3 on vista)

[ghisler(Author)]

The editor is still opened, so it can edit the file if it is already there (then the creation will also fail).

[sz]

i think it should work this way:

Code: Select all

file exists?
yes:no problem, start editor
no:{
  create file
  file exists (create succeeded)?
    yes:great, start editor
    no:issue warning
  }

[VadiMGP]

2sz

i think it should work this way:

It is impossible as general rule. Many editors use the same check to detect whether new file should be created or them should edit existing one. If file exists editor perform internal integrity checking. It this file was created by TC, this checking will fail.
For example, try to create manually empty .PSP file, open it in PainShop and see what happens.

[sz]

i was talking about "SHIFT+F4 Create new text file and load into editor" function, which creates a 0byte file (if it can create a file).
tcmd will create the same 0byte file, does not matter if its extension is .psp, xls, doc, or anything

[ghisler(Author)]

This should be fixed in RC1. Please test!

[sz]

works great, thanks

This should be fixed in RC1. Please test!

[ghisler(Author)]

Thanks for testing!