Thank you for your answer. However, your suggestion only makes sense for pure-text clipboard contents. However, let's say you simply go into explorer, select a file, and hit "ctrl-c" to copy it.
If you "type" it in TCC, TCC will report: "Clipboard is not text format"
On the other hand, in VIEW's View Clipboard box, you can see the full path and file info as it exists on the clipboard.
In general, the advantages of VIEW's View Clipboard box over "type clip:" are three:
1] The ability to view it in hex format
2] The ability to see the clipboard through the prisms of the various available retrieval methods (unicode text, oem text, windows drop handle, OLE private data), etc., to understand why various applications are reacting as they are to the clipboard.
3] Finally, as demonstrated above, the ability to see all formats of data, such as drop handles, graphics data [in hex format], etc., beyond just straight text.
If you are interested in the contents, you could simply 'type' it.
However that would only work with text data....