Just clicking on the Indexer icon...

Hmm. Just got a message about it being ready to install resources, and it didn't do it then (now on RC2).

Hi all.

Is it just me, or just merely clicking (right clicking!) on the indexer icon when it has updates ready to install cause it to close Logos? (Running RC1, about to install RC2 prompted me to send this).

Regards,

Nigel

Yea it shouldn't have done that, are you sure you didn't double click?

Well, we always accept history by faith too, don't we?!

I think I right clicked. I guess I'll have to wait until RC3 (assuming there is one). If I have the presence of mind, I'll create a snapshot of the VM so I can retest if I'm unsure.

It's happened for me like that several times, too.

It's happened for me like that several times, too.

Actually it's happening all the time for me now.  Either left or right click on the icon when it's ready to install causes Logos to close and the install begins.  It doesn't wait for me to select the Install menu item.

Same here

Steve

Ok I will ask about this and let you guys know.

Edit: One more thing, are you sure you aren't clicking on the balloon tool-tip that pops up when an update is ready? Clicking this tool-tip will initiate the install..

George what is the (technical) "difference" between them?

Which ever type this one is (and no matter what it says) whenever we get a mouse on it to either left or right click it is "poof" gone!

Steve

Ok I will ask about this and let you guys know.

Edit: One more thing, are you sure you aren't clicking on the balloon tool-tip that pops up when an update is ready? Clicking this tool-tip will initiate the install..

Usually don't see any tool-tip when this happens.

George what is the (technical) "difference" between them?

Which ever type this one is (and no matter what it says) whenever we get a mouse on it to either left or right click it is "poof" gone!

Steve

Here is the difference. Whenever a (balloon) tool-tip on the task bar shows up, it usually allows for a click on it to execute a function of the corresponding task-bar icon whatever the main funciton may be. Now if you see this tool-tip (I believe it is a balloon tool-tip with wavy corners and with an 'x' on the top right corner) if you click on the 'x' to close the tool-tip it will NOT execute that function. Thus when you click on the icon it will show the function Install Update in bold letters, bold letters means if you were to double click on the icon it (should) run that function, and therefore Windows tries to save you that extra step by providing this balloon tool-tip and by clicking it, it executes the default (bold) function.

This is why I need to know if you happen to be clicking on the icon when the (balloon) tool-tip is up. Because my computer does it too, when this tool-tip is up, however if there is no balloon tool-tip and you see just the regular tool-tip (small, square, one-line of text usually) this does (and should not) execute any functions.

QUOTE: This is why I need to know if you happen to be clicking on the icon
when the (balloon) tool-tip is up. Because my computer does it too,
when this tool-tip is up, however if there is no balloon tool-tip and
you see just the regular tool-tip (small, square, one-line of text
usually) this does (and should not) execute any functions.

George, Thank you for this detailed description. I  hope my memory is not failing me but I am pretty sure that it is the later situation.

I have seen the "baloon with the x" - I have closed that baloon with the x and EXPECT it to close when clicked on (as any x usually does).

BUT "The regular tool-tip (small, square, one-line of text
usually) this does (and should not) execute any functions." This is what I saw and tried to click.

I am almost positive that it was this smaller box.

[When I am not sure about something I always try to right-click with the assumption that it is a "safe" thing to do.]

Not this time -- Even trying to see if I could right click did not "work' as everything just "disappeared".This behavior "surprised" me - it was unexpected.

Again, George, I could be wrong as this was a few hours ago (but I am pretty sure that it has now happened twice to me)

Thanks

Steve

Yes this behavior surprises me too! I will speak with the devs. Thanks for following up.

Hi George.

I though that this was fixed yesterday, but with this morning's 50M resource update, I believe I saw it again. Would you please let the devs know? Perhaps it needs fixing in more than one codepath.

Thanks for all your work!