Mike Chaney's Tech Corner

http://www.ddisoftware.com/qimage-u

v2018.107  Jul 25, 2017

Priority: Low

2018.107 improves the appearance of print sizes for various skins and corrects a crash when using file name view (no thumbs).

Mike

Hi, thanks for the fix in this update.
I'm getting a problem though, after editing an image in qimage and selecting "apply the filter to current image", the image is being removed from the queue?  any ideas?
Thanks

Chris

Chris,
I get the same thing but I rarely use Apply  with images in the queue. I did it once but cannot now repeat it!!
There's not normally any need to use "Apply" if the View in the Editor is set to "Filtered Image". When you click the Next or Previous arrow, you are asked about saving the filter.
Terry

Hi Chris,
Terry asked if I had any idea I was invited.

I have a question.
When you say, being removed from the queue, are you sure it really was in the queue?
What happens to me sometimes, but I am not too sharp, instead of clicking on a + PLUS on a thumbnail, I double click the thumbnail.
This sends the image into the Editor just like it was in the queue. Except, When I save /apply filter, the editor closes and there's nothing in the preview screen/queue.

Maybe??

Fred

Another possibility:
If you accidentally unchecked the box that says IN QUEUE, that image would be dropped from the queue. See snap attached

Fred

Thanks for the suggestions.
Images are definitely in the queue, of example I put 8 images in the queue then edit 1 of them. After saving the filter (clicking DONE) there are only 7 images in the queue.  I repeated this until only 2 images left in queue.
I've just realised that if I click "next" rather than "Done" on the above example, then the image isnt deleted, but as soon as I click "Done" then that image is removed from the queue.
Regarding the "IN Queue" check box I tried it both ways and still resulted in removal from queue.

Thanks

Chris

Sorry, Chris,
I must have tried 25 times in as many ways as I could, and I cannot lose an image.
Fred

Thanks Fred.
It looks like I've missed the obvious first step....."reset ALL program settings" this seems to have solved the problem. I've loaded about 20 images in the queue and all seems ok now!
Sorry to have wasted your time  :(
Many thanks

Chris

Never happen
Thanks,
Fred

Here's a missed a step story.
I was creating a new folder in FCCM and accidentally used an = instead of a - dash in the filename.
QU ignores the folder most of the time.
Took a while before I saw it.

Fred

 ;D ;D

For what it's worth - I am having the original problem as described - if I edit an image that's in the queue and then exit the editor with the Done button - the image is removed from the queue _but the edit changes are applied, and then I just put the image back in the queue)  

UPDATE - but not all of the time! And, I can't find - at this point - any difference in the circumstances when it happens or not.  Will see if I can find anything resembling properties.

Hi Mel,
Just grasping at straws, but maybe it is important to try to reproduce. I never asked;
How do you enter the Image Editor?
I double click the big image on the print preview screen.
Others may use Right Click menu from the preview screen which has a few "entrances": "BATCH EDIT, EDIT IMAGES.
From the right click menu of the thumbnail side, we have EDIT IMAGES and even CUSTOM FILTER.
That's 5 ways to edit an image or get to Edit the image.
Maybe one of those is acting up?

Edit:  Edit   Another thought. You just made an adjustment; perhaps added 5 to DFS strength. The preview box is open. Do you click DONE now, or do you click OK first on the preview box and then DONE???

Fred

Fred -

Good thinking - or at least same thinking as mine so it must be good  ;D .  I actually thought I had it for a while.  I know that when it was happening, even though the image was sitting there on the preview screen, I was entering the editor by double clicking on thumbnail. Since then I have tried quite a few test scenarios involving most of the things you mention.  I can not reproduce the result now no matter what I do.  My habit is to always say OK to the preview box before I click Done.  Could I have forgotten that?  Possibly once - but in the session where I had the issue occur, it was happening repeatedly and I know that I would not consistently do that - too much habit as I always want to see the results of the edit on the full image..  Once I closed that session and then reopened QU, I could not replicate the behavior.

I will try a few more scenarios later today.

Mel

Mel,
We might be making progress..
Working on an image which was opened in the editor by double clicking the thumbnail, will result in the image no longer there by intent.
But, it was never in the queue if you double clicked it, so I am scratching head.
I still cannot make it happen here.
One other thing to mention, although it is out in left field.  (I have done this to myself so I know it is possible)
Let's say you have an image in the queue.  You double click the thumb and enter the editor.
You do your stuff making a few adjustments, and click DONE.
I can make the image disappear this way..........
If I accidentally clicked on the left arrow, wanting the first image in the queue, the print screen goes blank.
That would be the sample screen.
In the meantime, I double clicked the THUMB opening the editor with the image I double clicked on.

Do my adjustment, click done, and I have a blank print screen.
The adjustments have been saved. But you do not see the image in the queue.
Click one right arrow, and there it is....

Maybe????
Fred

Snap 3 image in queue, print screen
Snap 5 Image in the editor even though you clicked  left to Sample Screen
Snap 4 Imag in queue print screen after you closed Editor. Blank??

During the session when it was happening, it was definitely happening and I could actually watch the image vanish from the queue.  It was the only image in the queue.  When I clicked Done, I would again briefly see the image on the preview screen and the thumb would go blank for a second or two while it finished rebuilding.  Then when the new thumb appeared, ZAP, the image on the preview screen vanished.  I did this several times to make sure I wasn't doing something unusual. That's when I made my initial post about this yesterday.   But as I said, after I closed and restarted (normally) QU, I could not repeat this.  Till I try again in about an hour or so, I have nothing really intelligent to say about it - unlike the fountain of wisdom that I am usually.

While you are at the "fountain", I would like sundae with vanilla ice cream, and hot fudge with marshmallow and whipped cream.
Thank you.
Fred

Well Fred - I think I have a better chance of delivering that dessert to you still frozen in Florida than I do of repeating this issue.  Over the past 75 minutes or so, I have tried every reasonable and some unreasonable -  scenarios - even done some things with QU that are unnatural - probably against the law in half a dozen states - I cannot repeat the problem. I'm just going to go back to doing what I'm doing - if I can remember what that was. If it happens again - I'll try again to identify the environment.

Thanks for all of the suggestions

Mel

Well, I finally did have this phenomenon happened again - after almost 3 hours of continuous QU use in editing and printing pictures - one at a time 8x10s centered on letter size paper. When it finally happened I immediately repeated the exact same edit and sure enough it happened again. I then went through a series of one photo edits and thought I had actually found an answer - but probably not.  The "remove from queue" situation only happened when I changed contrast.  It never happened on edits when I did not change contrast.  However, in subsequent tests, it also does not always happen even if I do change contrast, so I am probably no closer to finding out anything other than this anecdotal ramble.  (and why should that matter - I would think the preview page would not care or act differently based on the content of the .flt file anyway)

If I find out anything useful, I will let you know

Mel,
Guess what?
I made the disappearing image disappear, just as you described.

I did it three times, and then I decided to make a video for Mike, and I couldn't do it on demand any more.

I had two in the queue. The second image had a crop and a cutout.  I adjusted the  location of the crop since that has a direct bearing on the location of the fade part of the cutout.
When I moved the existing crop up a half inch, QU sort of hung the crop and left the new location with the outline of the old location on screen.

I clicked DONE anyway, and Viola. Only one left in the queue.
I repeated it three times.   The image disappeared when the refreshed image did the "cluck cluck" to signal it was done rebuilding.

Since you have neen vindicated and no longer need that jacket with the laces in the back, don't throw it away. I might be looking for a used one.

Fred

As a great philosopher once said, oy vay!  I don't understand how this can happen.  A computer is supposed to do the same thing under the same scenarios.  I have not been back in QU since I made the previous comments but have been questioning myself since. Could I have accidentally moused over something and clicked (repeatedly?).  Could this somehow all have to do what else might me momentarily going on in the computer, like some kind of memory leakage thing? The thing is, when it happens I can more or less repeat it - for a while.  I just don't see how this can be a QU bug, but when I get back for my next session, if it happens, I'll try again to make some sense of it.

What about that laced up jacket?

Seriously, helping to debug stuff with Mike over many years, has rid me of the idea that a computer should do the same thing over and over.


That was true before the mouse.
The mouse rides over surfaces tickling various sensitive areas beneath it.
That is how we eventually evolved to making important use of video clips on how I made something happen.
Mike would watch the track of my mouse, and the speed of the cursor, and could repeat the problem.

That same philosopher, later in life was also quoted as saying: kishmere.... It happened here too!
Fred

Greetings! I'm still having this issue recalling some jobs from the log. However, I tried something today that worked. First, recall "Settings" only. Then recall "Job" (with images). That did not generate the stream of "Control has no parent" alarms.

EDIT: Sorry, this is not foolproof. I just tried to recall a job from a couple of weeks ago, "Settings" only and it threw the error.

Cheers!

Brad