OSX Don't close the application when closing Inkscape window
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Confirmed
|
Wishlist
|
JiHO |
Bug Description
Dear all,
I have a recently tweaked version of Inkscape 4.5 that will now save
files properly AND re-open them. Thank you!! However, the new program
takes forever to load even when the X-11 environment is up already. A
second characteristic that is VERY inconvenient is the fact Inkscape quits
completely if I close a file, NOT QUIT THE PROGRAM. Jiho was kind enough
to explain why this is so, but that doesn't make it right. I'm sure we'd
all like to be able to close a file and open another to continue working.
Right now, I have to go through a long wait for Inkscape to restart before
I can ask it to open a file for editing purposes.
I'd appreciate any assistance in these two matters.
Thank you for all your help,
Stg3
Changed in inkscape: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Originator: NO
The point I was making earlier is that, by design, each new document is Inkscape. app/Contents/ Resources/ bin/inkscape
attached to a new instance of Inkscape (Inkscape functions as a SDI: Single
Document Interface). Therefore, opening a new document starts the whole
application. On OS X there is an additional level: the application wrapper
(i.e. what you see in the doc which launches the Inkscape binary when you
click on it). This application wrapper is just a small bach script and some
OS X added goodness (icons etc.) and this does not take much time to run.
So to conclude, keeping the OS X wrapper alive when you close a document
will be more consistent with the rest of OS X interface but won't solve
your startup time issue anyway.
So what are the solutions:
1/ did you try an official Inkscape build for Panther? The first that was
with the dev builds had debug information which makes the app bigger, hence
longer to start.
2/ fill a feature request (rather that a bug report) to ask for keeping
the application wrapper alive. This probably won't happen soon but would
indeed be a nice thing to have (once again it wonmt solve the startup time
problem though).
3/ give us some benchmarks on the startup time of a debug info-free
Inkscape on your system so that we can compare to what happens on ours (+
some info on your hardware: which model, how much ram, which processor
speed etc.). A good way to have a precise timing is to use the terminal. If
Inkscape is in your Applications folder, just run:
time /Applications/
and close Inkscape as soon as the window appears completely.