#4 File->Close causes KXStitch to quit

Andy Piper

Presumably File->Quit should cause KXStitch to
shutdown, and File->Close should just close the current
file (and leave an untitled new canvas if necessary,
but leave KXStitch open). At the moment KXStitch quits
when File->Close is selected.


  • Stephen Allewell

    • summary: File->Close causes KXStitch to quit --> File->Close causes KXStitch to quit
    • status: open --> closed
  • Stephen Allewell

    Logged In: YES

    This is a debatable issue. If the user closes the document
    and it is the only one open, I don't believe that KXStitch
    should prempt the user and assume they want to work on
    another pattern, therefore KXStitch consequently closes. If
    the user does want to work on another pattern then use
    File->New or File->Open.

    It is the differentiation between the KXStitch application
    process and the pattern editor main windows that the user
    actually sees.

    When the user first starts KXStitch, the application process
    starts, this in turn creates an instance of the main window
    that the user can interact with.

    Ideally KXStitch should have a File->New Window menu item,
    which will create a new instance of the Main Window under
    the ownership of the KXStitch application process.

    Alternatively the user can start a new KXStitch application
    process, which in turn creates a new main window.

    Now the use of File->Close and File->Quit makes more sense.
    If a single process creates several main windows, using
    File->Close will close the corresponding main window but
    leave the other main windows under the same process still
    running. Using File->Quit will close all the windows
    running under this process, and consequently the process
    itself will finish, but won't have any effect on other
    KXStitch application processes, and their related main
    windows, that were started.

    Does this make sense?


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks