1. No start menu shortcuts for StartisBack. I have to go to C:/Program Files (x86)/StartisBack to open the StartisBack. It is difficult to find the tool for beginners and time taking for advanced users too, till they create short cuts.
I know you directly addressed Tihiy, but I'm going to respond anyway.
Hope you don't mind.
What shortcut is necessary for StartIsBack? Once installed it runs automatically. Configuring StartIsBack is just like configuring the Windows 7 Start Menu, right click either on the Orb or the Start Menu itself and choose Properties.
2. In StatisBack configuration, under Start Menu Power default actions, there is no way of setting Hibernate as default. Hibernate is not at all in the list but it still exists on start menu.
Seconded. I use Hibernate often and although at this current moment I prefer the power default be Lock, if I ever change that again it would probably be to Hibernate.
3. Not 64bit application. The 32bit works on 64bit but having a native 64bit edition add value to the tool as some might not like 32bit apps on 64bit machine.
The configuration program might not be 64-bit but StartIsBack itself has both 32 and 64-bit DLLs for the appropriate system. It is the DLLs which actually make StartIsBack work. Personally, I don't think there's reason enough to make a 64-bit version of the configuration program. It's a tiny program and certainly doesn't make use of more than 4GB of RAM. Unless someone can think of reasons which are more than aesthetic...?
4. The term Modern UI make it feels like the App is Windows 8 UI fan. It makes me feel like Windows 8 UI is modern and Windows 7 UI is traditional. Why not just say Windows 8 UI instead. Modern UI is a vague word to understand in as it doesn’t refer to anything.
Although it's confusing, Microsoft is who calls it "Modern UI" (previously known as Metro). It's already confusing enough without adding any more aliases for what it's called.
Under Modern UI, “use hotkeys to invoke Start Screen:” it is useful but it doesn’t turn off metro completely! To know if metro exists or not after unchecking that command, I just opened a video with the metro – video app. It opened it without any problems. The metro is still there! So would you add another command to completely kill this tablet metro? To avoid not implemented error messages when using metro apps from desktop, it is better to completely remove them from associated programs list, if possible. Say when I click on open with on a video file, I shouldn’t see video metro app. Thus the “not implemented “error will go away!
Tihiy (and anyone else) who kills Metro completely will then experience problems with some portions of the Desktop UI, which use parts of Metro to display, for instance, Wireless Networks, new drive detected interface (AutoRun) and other elements. This was one of the problems Tihiy fixed to the best of his ability in Ex7ForW8. SiB couldn't remain as elegant and direct as it is right now if Metro would actually be disabled. He'd then have to re-implement the "toast notifcations" just as he did in Ex7ForW8.
If he chooses to implement that possibility at some point or even soon, that's his choice and as long as the user can decide whether or not to turn Metro completely off or not, I don't think anyone would have any serious problem with it, but I doubt if that's a high priority on his to-do list.
Edited by roirraW "edor" ehT, 20 November 2012 - 06:55 AM.