The problem is Windows (cmd.exe) keeps keystrokes in the keyboard buffer when it probably shouldn’t. In other words, DTI is behaving exactly the way a Windows program is supposed to behave. Count the number of bytes or packets sent and received. Unzip the downloaded ZIP file and selectAppNetworkCounter.exe file and you can use the application. Press TAB then SPACE again and watch the next CONTROL trigger.Ĭlick on the cmd.exe CONTROL, type exit and enter. AppNetworkCounter can be used without installation. Press TAB then SPACE and watch the next CONTROL trigger. Press the SPACE bar and watch the first CONTROL trigger. So the issue seems to be that at some arbitrary point in time DTI receives a key down message from Windows and dutifully sends it to the control that currently has focus.Ĭlick on one of the CONTROLS then close that window. It’s not waiting around for the external process to end, it’s long forgotten about it. Remember DTI merely starts the external process and goes right back to pondering it’s navel. In fact you can use the TAB key to move the focus to the next control, you just can’t see the focus rectangle but it’s still doing it. The controls react to keypress as they should, as does any Windows program. For every application, the following information is displayed: the number of sent and received bytes, number of sent and received packets, number of sent/received IPv4 bytes, and. The keyboard buffer issue is an interesting one. AppNetworkCounter is a simple tool for Windows that counts and displays the number of TCP/UDP bytes and packets sent and received by every application on your system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |