Alex,

3893 regards general UI design, where different opinions exist (I tend to yours, but I am not deciding).

3921 could not be reproduced, and as long as it only happened once to you, it cannot be excluded, that this was a coincidenting IIS issue.

Please note, that he DotNetNuke Core Team has limited resources, that needs to be focused by priority.

Thank you for your support.

Thanks Sebastian and Charles.

I see your points...

3893 - My overall point is basically the UI should be made a consistent as possible. I realise it's hard because everything is still under development but certainly effort is needed here. Of course I can understand if the team is stretched and something must give (know the feeling!).

I have now logged all the UI stuff under a proposed enhancement here:
DNNP-3962

Note I've extended it and changed it and hopefully it is a little more suitable for the Gemini forum. 

3921 - The two URL's I gave when I initially logged the issue shows how you could trap the error in the Windows Application log just before IIS crashes (or am I wrong here?). Perhaps this could be vital for diagnosing when something in the scheduler crashes. My particular issue here was not important, but I wondered if this sort of error could be trapped to help in future diagnosis. Then again I could be way out - sorry. Care to comment on this again?

Cheers!

Alex