06-23-2011, 03:50 AM -
I disagree that this alledged 'bug' should not be fixed!
I work for a company whose product is used on thousands of public PC's and we recommend StartKiller as a means to 'KILL' the start button and prevent access to the Start Menu.
Our product already disables the windows key as an optional, configurable feature, plus disables many other keyboard combos, what our customers needed, in addition, was a product to completely stop users from gaining ANY mouse access to the start button whatsoever! Rather than trying to develop a product that may be covered by an existing product, we came across StartKiller and have happily recommended your product to our customers who wish to completely stop public users from accessing the start button and or menu.
Some will use registry hacks, some will use local or group policies to disable start menu options and enforce other restrictions to stop the public from gaining access to programs via the startmenu they do want public users to access.
In my opinion most people use StartKiller for one or both of two reasons...
1. To hide the start button and menu to provide extra space on the taskbar but still access the start button and menu as and when required.
2. To Comletely KILL the start button or access to the start menu
It has been reported today that this 'bug' (and it is a bug in my opinion) allows users to access the start menu using the mouse and in a public environment this is NOT the required behaviour from StartKiller.
I believe very strongly that this issue should be resolved and that it should be an optional feature so that users of StartKiller can choose to completely block access to the start button or not if they wish.
By providing a product that appeals to a wider base of users cannot be a bad thing?
If this issue is not going to be fixed, maybe you should consider renaming StartKiller to something else, because it does not 'kill' the start button completely.
If it is not possible to resolve this issue, then please, just say so.
I work for a company whose product is used on thousands of public PC's and we recommend StartKiller as a means to 'KILL' the start button and prevent access to the Start Menu.
Our product already disables the windows key as an optional, configurable feature, plus disables many other keyboard combos, what our customers needed, in addition, was a product to completely stop users from gaining ANY mouse access to the start button whatsoever! Rather than trying to develop a product that may be covered by an existing product, we came across StartKiller and have happily recommended your product to our customers who wish to completely stop public users from accessing the start button and or menu.
Some will use registry hacks, some will use local or group policies to disable start menu options and enforce other restrictions to stop the public from gaining access to programs via the startmenu they do want public users to access.
In my opinion most people use StartKiller for one or both of two reasons...
1. To hide the start button and menu to provide extra space on the taskbar but still access the start button and menu as and when required.
2. To Comletely KILL the start button or access to the start menu
It has been reported today that this 'bug' (and it is a bug in my opinion) allows users to access the start menu using the mouse and in a public environment this is NOT the required behaviour from StartKiller.
I believe very strongly that this issue should be resolved and that it should be an optional feature so that users of StartKiller can choose to completely block access to the start button or not if they wish.
By providing a product that appeals to a wider base of users cannot be a bad thing?
If this issue is not going to be fixed, maybe you should consider renaming StartKiller to something else, because it does not 'kill' the start button completely.
If it is not possible to resolve this issue, then please, just say so.