workaround: change all affected extension associations from notepad.exe (i.e. notepad++ launcher) to notepad++ itself --> launcher issue
possible reason: IZArc creates a temporary file and invokes the associated application. When "the application" returns it deletes this file. This works fine of course if "the application" is the editor (notepad++) itself. The launcher however, may return (after having invoked notepad++) at a time notepad++ has not yet opened the file.
--> From IZarc's point of view the launcher is "the application" and deletes the file *before* notepad++ has opened it. So it's a question of timing (how fast ist the editor redirect compared to to the archiver delete) if this combination works or not.
If this is true the launcher should not return before notepad++ itself does.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Windows XP SP2
IZarc 3.7
Notepad++ v4.0.2
Notepad launcher properly(?) installed (works in all other cases)
Hi all,
I get a cross problem when using Notepad++ with IZarc to view txt files from within archives (or other files that are directly linked to Notepad(++)).
When I double-click on a txt file I expect the file to be temporarily extracted and shown with Notepad++.
What happens here is:
1. I get "create new" message:
The file "<IZarctemppath>\filename.txt" doesn't exist. Create it?
2. If I click "Yes" Notepad++ crashes immediately.
If I click "No" I get of course an empty sheet.
Furthemore, Notepad++ may crash on closing the document or not.
I haven't yet understood this behaviour. It may depend on Notepad++ settings.
This seems not to happen neither if I use another archiver nor another editor ...
Stephan
Nice find. Thank you for letting the rest of us know in case we encounter it ourselves in other situations. --Joel
Partly found the reason and a workaround myself.
workaround: change all affected extension associations from notepad.exe (i.e. notepad++ launcher) to notepad++ itself --> launcher issue
possible reason: IZArc creates a temporary file and invokes the associated application. When "the application" returns it deletes this file. This works fine of course if "the application" is the editor (notepad++) itself. The launcher however, may return (after having invoked notepad++) at a time notepad++ has not yet opened the file.
--> From IZarc's point of view the launcher is "the application" and deletes the file *before* notepad++ has opened it. So it's a question of timing (how fast ist the editor redirect compared to to the archiver delete) if this combination works or not.
If this is true the launcher should not return before notepad++ itself does.