Just installed the latest release of Luminar. Why does FILE > CLOSE terminate the application? FILE relates specifically to the current file activity, not program activity. If you want to Quit the program you should hit QUIT LUMINAR 3 which is designed to exit the program. FILE > CLOSE should only close the current file you are working on and exit to the library or offer you the option to SAVE or Discard Changes, NOT terminate the program. This is a program functionally BUG! I first noticed this with release 3. I reported it to Skylum then and was told that that's the way the program is supposed to work. I reported it again with 3.1 and was told that the problem had been turned to their developers. I reported it again with 3.1.1 and once again was told that's the way the program currently functions but the problem had been turned over to their developers. This is the only program I know where a basic function dealing with FILE functionally terminates the program. I guess they really don't consider it an issue or the code is convoluted and difficult to fix.
Does anyone have an earlier version of Luminar? If so, does FILE > CLOSE terminate the program? Curious to see how long this has been occurring. It might explain why it is so difficult to correct.
Mac
Loc: Pittsburgh, Philadelphia now Hernando Co. Fl.
[quote=dwermske]Just installed the latest release of Luminar. Why does FILE > CLOSE terminate the application? FILE relates specifically to the current file activity, not program activity. If you want to Quit the program you should hit QUIT LUMINAR 3 which is designed to exit the program. FILE > CLOSE should only close the current file you are working on and exit to the library or offer you the option to SAVE or Discard Changes, NOT terminate the program. This is a program functionally BUG! I first noticed this with release 3. I reported it to Skylum then and was told that that's the way the program is supposed to work. I reported it again with 3.1 and was told that the problem had been turned to their developers. I reported it again with 3.1.1 and once again was told that's the way the program currently functions but the problem had been turned over to their developers. This is the only program I know where a basic function dealing with FILE functionally terminates the program. I guess they really don't consider it an issue or the code is convoluted and difficult to fix.
Does anyone have an earlier version of Luminar? If so, does FILE > CLOSE terminate the program? Curious to see how long this has been occurring. It might explain why it is so difficult to correct.[/quote
This is off a PC
I have a earlier 2018 version and the latest version. The earlier 2018 version allows you to save the liminar working file (File > Save). Use File > Exit to terminate the program. The latest version auto saves the working file in it's catalog folder (open Explorer > this computer > pictures > luminar catalog). In my versions there is no File > Close. I'm running on a PC though.
Kaib795 wrote:
This is off a PC
I have a earlier 2018 version and the latest version. The earlier 2018 version allows you to save the liminar working file (File > Save). Use File > Exit to terminate the program. The latest version auto saves the working file in it's catalog folder (open Explorer > this computer > pictures > luminar catalog). In my versions there is no File > Close. I'm running on a PC though.
Looks like there is definitely a difference between the Mac version and the Windows version. I reloaded Luminar 2018 on my Mac and tried the FILE > CLOSE and it worked just fine. It closed the file as expected. Looks like when they went to Luminar 3 they screwed up the FILE > CLOSE option on the Mac version. I would actually expect the program to offer close options and then close the file and go back to the browsing the library. I mentioned this to Skylum tech support and got a very curt response. "For now, File > Close has the functionality of closing the app." That's their answer for now. I must be expecting a little too much.
Just so you know, I have no close file to select on my PC. I click on the icon under the File menu and select ... I think it's ... remove from quick edit. And it's still on the screen but gone from the left thumbnail area. If the program gets funky I just restart the app. Understand this is cheap software and you are getting a lot for the money. In the old days this would happen in Photoshop and the screen would lock up and you lost everything. This new version auto saves and for many it's a blessing but for me I need to have it auto save to the Luminar catalog folder on another HD externally. I know what to do now. It's still nice software if you don't do heavy edits. Oh and when it gets slow or doesn't function properly, usually after I do my second save as a different resolution but the auto save has it so I just restart the app and it's okay. Go easy on all that color saturation, this is where most get carried away and post NOT AS SEEN stuff (fluorescent greens). Just use the overall % slider to pull it back to earth! LOL
Kaib795 wrote:
Just so you know, I have no close file to select on my PC. I click on the icon under the File menu and select ... I think it's ... remove from quick edit. And it's still on the screen but gone from the left thumbnail area. If the program gets funky I just restart the app. Understand this is cheap software and you are getting a lot for the money. In the old days this would happen in Photoshop and the screen would lock up and you lost everything. This new version auto saves and for many it's a blessing but for me I need to have it auto save to the Luminar catalog folder on another HD externally. I know what to do now. It's still nice software if you don't do heavy edits. Oh and when it gets slow or doesn't function properly, usually after I do my second save as a different resolution but the auto save has it so I just restart the app and it's okay. Go easy on all that color saturation, this is where most get carried away and post NOT AS SEEN stuff (fluorescent greens). Just use the overall % slider to pull it back to earth! LOL
Just so you know, I have no close file to select o... (
show quote)
Luminar 2018 was working correctly. They seem to be breaking a working product. I understand what you are saying, however, I was a software developer for years and understand the complexities of product development. Regardless of what a piece of software costs, it should perform as advertised or corrected as soon as a problem is identified. I identified this specific problem within days of the first release of version 3. They have had 2 upgrades since then, and still no correction. I think their actual problem is that they have two "different" versions of the program (Mac & Windows) trying to perform the same thing. They might even have two different sets of coders or worse yet two different coding languages ("Object C++" & "Swift"). That could spell disaster in the long run. Will wait and see.
As for different platforms, Adobe has done it for years with little problems. Luminar folks do listen to me and try to address my problems right away. I think their support is pretty good. On the flip side Adobe has been excellent and has walked me through fixes before and one time took over my computer to fix it themselves. If you ever move to LR and PS let me know and I'll steer you to this online guru who is a great teacher.
dwermske wrote:
Just installed the latest release of Luminar. Why does FILE > CLOSE terminate the application? FILE relates specifically to the current file activity, not program activity. If you want to Quit the program you should hit QUIT LUMINAR 3 which is designed to exit the program. FILE > CLOSE should only close the current file you are working on and exit to the library or offer you the option to SAVE or Discard Changes, NOT terminate the program. This is a program functionally BUG! I first noticed this with release 3. I reported it to Skylum then and was told that that's the way the program is supposed to work. I reported it again with 3.1 and was told that the problem had been turned to their developers. I reported it again with 3.1.1 and once again was told that's the way the program currently functions but the problem had been turned over to their developers. This is the only program I know where a basic function dealing with FILE functionally terminates the program. I guess they really don't consider it an issue or the code is convoluted and difficult to fix.
Does anyone have an earlier version of Luminar? If so, does FILE > CLOSE terminate the program? Curious to see how long this has been occurring. It might explain why it is so difficult to correct.
Just installed the latest release of Luminar. Why ... (
show quote)
Why not tell Luminar about your thoughts??? I don't think it's anyone on the Ugly Hedgehogs fault!
This was discussed at length yesterday. Workaround: To edit another photo, choose File > Open Images for Quick Edit (Command-O on Mac) or click on another image. It took Adobe years to fix a similar "feature" in Lightroom.
I find it easiest to simply change to gallery view once I've finished with an image and double click the next image I want to display and edit. Remember all changes done to an image are saved in the history and so once I've finished working with an image I just move on.
L 3.1.1 is a good improvement and IMHO deserves more than a 0.01 version change. I spend less time on the computer and more time "living real life" so I say hats off to Skylum.
xt2
Loc: British Columbia, Canada
dwermske wrote:
Just installed the latest release of Luminar. Why does FILE > CLOSE terminate the application? FILE relates specifically to the current file activity, not program activity. If you want to Quit the program you should hit QUIT LUMINAR 3 which is designed to exit the program. FILE > CLOSE should only close the current file you are working on and exit to the library or offer you the option to SAVE or Discard Changes, NOT terminate the program. This is a program functionally BUG! I first noticed this with release 3. I reported it to Skylum then and was told that that's the way the program is supposed to work. I reported it again with 3.1 and was told that the problem had been turned to their developers. I reported it again with 3.1.1 and once again was told that's the way the program currently functions but the problem had been turned over to their developers. This is the only program I know where a basic function dealing with FILE functionally terminates the program. I guess they really don't consider it an issue or the code is convoluted and difficult to fix.
Does anyone have an earlier version of Luminar? If so, does FILE > CLOSE terminate the program? Curious to see how long this has been occurring. It might explain why it is so difficult to correct.
Just installed the latest release of Luminar. Why ... (
show quote)
It is a bit unusual, however, there are several ways too close a photograph, etc. without terminating the program. I guess as one gets accustomed to the new software it will become the "new" norm?
The point was, they broke or for those politically correct, "refined an existing feature" and it no longer functions. I have contacted them, on three previous occasions, V3, V3.1, & now V3.1.1. Now, if that is good customer service, then I think you need to go back to Adobe since, by other accounts, they took years to fix a similar problem in Lightroom. Yes, the FILE > CLOSE issue is a trivial one but it's always the lack of attention to the little details or the small cracks that lead to bigger issues within an organization.
My Luminar program has notified me that release 3.1.1 is available for download. When I try to download and install the new version, it doesn't do anything. Any advice /suggestions are appreciated.
dwermske wrote:
Just installed the latest release of Luminar. Why does FILE > CLOSE terminate the application? FILE relates specifically to the current file activity, not program activity. If you want to Quit the program you should hit QUIT LUMINAR 3 which is designed to exit the program. FILE > CLOSE should only close the current file you are working on and exit to the library or offer you the option to SAVE or Discard Changes, NOT terminate the program. This is a program functionally BUG! I first noticed this with release 3. I reported it to Skylum then and was told that that's the way the program is supposed to work. I reported it again with 3.1 and was told that the problem had been turned to their developers. I reported it again with 3.1.1 and once again was told that's the way the program currently functions but the problem had been turned over to their developers. This is the only program I know where a basic function dealing with FILE functionally terminates the program. I guess they really don't consider it an issue or the code is convoluted and difficult to fix.
Does anyone have an earlier version of Luminar? If so, does FILE > CLOSE terminate the program? Curious to see how long this has been occurring. It might explain why it is so difficult to correct.
Just installed the latest release of Luminar. Why ... (
show quote)
---------------
I have Luminar 3.1.1 and also an earlier version on computers and neither one has any "File|Close" option at all. In both cases I have a "File|Exit" option which is to close the program. I am runnin Windows versions so I don't know if what you mention applies to a Mac or not.
I am fed up with Luminar. 2018 works, but Luminar 3 freezes on My PC and will not open at all on my IMac
If you want to reply, then
register here. Registration is free and your account is created instantly, so you can post right away.