>But, programmaticaly, after my process, I will still need to remove this >transparent shape. So, after all this process (including the original one + >the line to remove the transparent shape), what is queued will be fired. >So, the problem remains. Remember, everything that is queued will be fired >when the interface become available. So what? Have some dummy code in the shape's Click method, so the clicks will be wasted. And after your process make a, say, 2 second break before you discard the shape. Could work. This invisible shield seems like a cute idea to me.