Unfortunately, that is not the error message that both John and I asked you to post. it is a shot of part of the folder structure in Photo Manager!
Did you read carefully the full list of file types which @johnebaker posted? If so, you will see that no RAW files are readable by PM (.CR2 and .ARW are both examples of such files).
Unfortunately, that is not the error message that both John and I asked you to post. it is a shot of part of the folder structure in Photo Manager!
Did you read carefully the full list of file types which @johnebaker posted? If so, you will see that no RAW files are readable by PM (.CR2 and .ARW are both examples of such files).
Jeff
There were 2 questions: one for the message ""No global memory in MyAllocGlobal" which I understand now is because I try to handle RAW files (which is not supported by Photo Manager), and the second question was about the flag on the folder, in the structure of folders. My question was: what that flag means? Thanks
The answer to the question about the flags (thank you for the screenshot): I honestly have no idea, sorry. I've never seen that before and I don't see it in my installation of PM - I just opened it to check - I thought it might be because you are using the Calendar option but I cannot reproduce it.
IF the error message "No global memory in MyAllocGlobalPtr for type 30" is due to an inability of Photo Manager Deluxe to handle a specified file, why doesn't the application simply make a note of it and continue processing remainder of photos...rather than hanging up the process waiting for the user to click on "OK" in order to keep the process running?
why doesn't the application simply make a note of it and continue processing remainder of photos
Presumably because it needs to be sure the user is aware of the problem? Imagine the number of users who would complain if the app simply "ignored" files it cannot open and didn't alert the user immediately. If the error message appeared only after all the scanning was complete, how is the user to know exactly which files have "failed", unless any or all were specifically listed? And what about if there was another, different problem with a another file?
I, for one, would far rather be alerted immediately to any problem, not be told after the scan is finished, when one might assume everything has gone OK.
When you begin analysis at 10pm on a directory having 6,000+ photos realizing that it will take a long time for the process to complete, thinking you will wake in the morning to find the analysis has been completed...only to find that 1/3rd of the way to completion the analysis process has stopped, hung up due to an insignificant memo about one file it couldn't analyze...I find that very disappointing. There's no need to present such a warning in the middle of the night when no one is watching! I would be satisfied to see each of these encounters tallied into a listing that could be presented to the user at the end of the analysis...at which point we could inspect each finding and be comforted with the results! Thank you.