- Dec
- 51
- 2
When using OSD /N [/TIME=x] to put text on the desktop asynchronously, the /C flag fails to clear the display. This new behavior appears to have happened as a result of one of the recent fixes to OSD.
Here's a script that demonstrates:
Note that there is some internal state change caused by OSD /C. If you try another one with no intervening OSD output, it throws an error. (I would expect it would just be a silent no-op, since clearing a display that is empty or nonexistent should be visually the same as doing nothing.)
Using different /ID=# or other args doesn't seem to affect this.
Version Info:
TCC 15.01.50 Windows XP [Version 5.1.2600]
TCC Build 50 Windows XP Build 2600 Service Pack 3
Here's a script that demonstrates:
Code:
@echo on
OSD /N `Test 00`
delay 2
:: this line has no effect--
OSD /C
:: this line throws an error--
OSD /C
delay 2
OSD /N `Test 01`
delay 2
OSD /C
delay 2
OSD /N `Test 02`
delay 2
:: you should find the effect of the following interesting as well...
OSD /N ` x`
delay 2
OSD /C
delay 2
OSD /N `________`
delay 2
OSD /C
Note that there is some internal state change caused by OSD /C. If you try another one with no intervening OSD output, it throws an error. (I would expect it would just be a silent no-op, since clearing a display that is empty or nonexistent should be visually the same as doing nothing.)
Using different /ID=# or other args doesn't seem to affect this.
Version Info:
TCC 15.01.50 Windows XP [Version 5.1.2600]
TCC Build 50 Windows XP Build 2600 Service Pack 3