Is it me or have they stopped making keyboards that clunk and make tapping noises? And why must mice be wireless - the batteries just keep running out. My grand mother recently bought a new PC that was completely touch-screen operated, I honestly cant imagine how this could be used in a practical environment. It felt uncomfortable to use and I am sure having a screen that close to you cant be any good for your eyes either. Eventually we both agreed that it was in-practical and she ended up using a USB-keyboard and mouse for her brand new touch screen computer. That said, I really feel touch screen is practical for mobile devices though (Where it's not practical to have a mouse). I used to think all new stuff would be cool and i'd grow into it. Is it me? Or is the next generation of computer users rejecting these newer input devices as well?
I find myself using my old PS/2 Logitech keyboard that's about 6 or 7 years old because I cant find a similar keyboard that has the same key resistance and 'clunkyness' in the newer ones. It is embarrassing to show people who come over though. My friends often say "nice setup.. whoa.. that keyboard looks ancient!". I am starting to feel like an old man - next I will be saying "They don't make em they way they used to!".
I visited one of my friends and he bought the latest in the logitech series of keyboards. (sounded like a terminator model) It had about a thousand different functions and an on-board LCD screen.. All I could say is.. Really.. is that necessary? Why would you look at the LCD screen on your keyboard? I went to use his keyboard and it felt horrible - there was hardly any resistance and it was completely silent. Maybe that's a good thing? Am I the only one who enjoys a good 'clunk'?
)...
You see, I'm from Mexico, hehe)
I don't know if it is important, but when i startet ViGlance and it worked again, I had SBar running, another Superbar simulation tool. Maybe running SBar and ViGlance simultaneously fixes the bug
Comment by Karrypto -August 16 2010 @ 12:50 pm
I don't know if it is important, but when i startet ViGlance and it worked again, I had SBar running, another Superbar simulation tool. Maybe running SBar and ViGlance simultaneously fixes the bug
Comment by Aaron7pm -August 16 2010 @ 12:53 pm
I don't know if it is important, but when i startet ViGlance and it worked again, I had SBar running, another Superbar simulation tool. Maybe running SBar and ViGlance simultaneously fixes the bug
If ViGlance works I don't, don't worry!
Comment by Karrypto -August 16 2010 @ 12:55 pm
I found another bug I think. After starting the computer from hibernate the StartOrb was invisible and only appeared when moving the mouse over it. Also I read somewhere here that there should be the possibility to start multiple apps. It's not in the right click menu, so how is it done? Please add it to the menu too! Also why is the working place icon shown for the explorer? I think this is a different icon in Vista in 7, isnt it?
Comment by wesp5 -August 16 2010 @ 01:46 pm
The empty taskbar and flashing taskbar seems to be the most common bugs happening in the latest build. Lee has mentioned that he has fixed the empty taskbar in build 1276, that is yet to be release. I myself have yet to experience this, and I am testing them on 3 computers. My Viglance seems to automatically set to Compatibility mode with XP SP2. I have a shortcut in the Start Up folder for Windows Start Up instead of checking the Start with Windows in the Option Dialogue. Unsure if this may help anyone though.
Coming back from hibernate may cause problems, not only for Viglance but other applications as well. Since hibernate causes a computer to store it's Ram information into the Hard Drive, and upon waking up, some dynamic (Real time apps) Ram information may run into problems.
To start a new instance, you have to Shift + Left Click. I have already suggested the use of the middle mousse and one in the context menu for the new instance to Lee and he may consider it in one of the future builds.
Comment by Rainoffire -August 16 2010 @ 03:28 pm
Forgot to answer this in my previous post. Couldn't edit it in also...
Anyways, Working Place's parent application/executable is Explorer.exe, so the icon would be that of Explorer. Working Place is simply a special folder in explorer. Could be in a similar situation for Control Panel items, simply being special locations and having Explorer as the parent.
In itself, it may be difficult to program Viglance so it would separate such special actions, and having it do that may have consequences when it tries to handle regular folders.
Comment by Rainoffire -August 16 2010 @ 03:49 pm
Maybe Lee could look into Tclock2 which manipulates the StartButton and works fine with hibernate.
Ah, thanks. But is this the same in 7? When does MS learn that something like this isn't intuitive!
I'll second the context menu but don't know about the middle mouse button unless it's on 7 too.
Comment by wesp5 -August 17 2010 @ 02:04 am
Update: Another small issue. In the classic look the icons are a big too large for the one line taskbar and stick out of the screen of the bottom and in the two line taskbar they are a little bit too far towards the top, so they don't look centered. Just nitpicking but at least the second issue should be very easy to fix
. Also I noticed that drag&drop of stuff still doesn't work. This would be easy to fix by having the application the mouse is hovering over with a dragged item just come to the front.
Comment by wesp5 -August 19 2010 @ 02:23 am
if ViGlance start with Windows automatically, sure that the original taskbar is "behind him":
Comment by Birkuc -August 24 2010 @ 11:49 pm
another problem:
sometimes, in very various situation, all the ViGlance taskbar icons disappears, but the program is not closed, and when you right click on the system tray icon the taskbar icons comes back, this thing happens average 5 times per day, so its not a big error but frustrating
what do you think, an "Always on top" settings (like for example CTRL+A in WinAMP) can solve this issue?
Comment by Birkuc -August 31 2010 @ 01:19 am