It is currently Sat Dec 16, 2017 4:03 am

All times are UTC - 8 hours [ DST ]


Forum rules


Before posting a bug report or a feature request, search the forum for an older post on the same topic. If you are reporting a crash, try capturing a crash dump. You can find instructions here: How to capture crash dumps



Post new topic Reply to topic  [ 1 post ] 
Author Message
PostPosted: Fri Feb 01, 2013 3:52 pm 
Offline

Joined: Fri Feb 01, 2013 3:41 pm
Posts: 5
If you click the Start button, then in the run/search box type a UNC path (e.g. \\foobar). When you press enter ClassicShell attempts to access this network resource, but there is no visual feedback to the user that it's doing anything. If the network resource is inaccessible then ClassicShell sits there for 15 seconds with no visual feedback. This leaves the user wondering if they actually hit the enter key or not. Compare this to the Windows Start menu, when you press enter immediately the Start menu closes letting the user know they did indeed press the enter key. ClassicShell should do something similar, either close the Start menu, or even something as simple as display the "working in the background" cursor.

This is a minor gripe for such as awesome program. But I have close to a dozen computers in my office and often times machines are turned off, so I run into it a lot.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 1 post ] 

All times are UTC - 8 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group, Almsamim WYSIWYG Classic Shell © 2010-2016, Ivo Beltchev.
All right reserved.