Remove all message boxes

Question

How about replacing all the message boxes with something like (and i can't believe i'm saying this) the information bar from internet explorer in the sense that you wouldn't need to click OK or whatnot to be able to continue your work.
Here's an example:
With the brush tool selected, you click by mistake in the image while a vector layer is selected. What happens? you get a message box telling you to rasterize the layer to continue. You click cancel because it's a mistake and then you get another message box telling you that you can't edit the layer (isn't it fun?).
This would be replaced by showing you a bar at the top of the image when you click on the vector layer telling you that if you click again with it on the layer you will rasterize the layer. The thing is that if you select a different tool or layer, the bar would disappear(as well as the effect of rasterizing by clicking once more in the image) without the need to click in some specific area before you can continue with your work.
The end result is that we'll be able to work faster and smoother. No more click ok for stuff like "no pixel is more than 50% selected", "could not complete because the area is empty", "cannot paint on hidden layer", "cannot continue because no layer is selected", etc

Answer 1

Here's another example where this status bar would be useful:
With a multi-layered document you go to Image->Mode->Lab and instead of asking you whether to flatten or not, it will automatically convert the image without flattening and show the bar saying something like "if the appearance doesn't match and you want to flatten the image then click here". And if you click on the bar it would redo the conversion but this time flattening the file before going to Lab. Also add an option in the bar to reverse the behavior of the conversion so that it automatically flattens the file and gives a bar saying the opposite to make sure that you won't get any angry users that always flatten when going to Lab or some other color space
Something similar would be when running actions that include a stop. Instead of relying on the user to know that he has to click play to continue or the creator of the action to write that when making the action, the bar would appear and tell you to click on it to continue the action after having made the necessary adjustments 
I for one prefer the bar to appear only when needed instead of it always being onscreen and taking up screen space but at the end of the day, as long as it's implemented i won't mind the exact method of the implementation.