Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to Shell_NotifyIcon WITHOUT adding an icon in the notification area
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. COYour quote specifically says you can't do this - I don't understand what your actual question might be: "The docs say I can't, but I want to anyway. How?" If you could hijack an existing notification icon, that would be a pretty wide security hole for malware, don't you think? Voting to close as "not a real question".
      singulars
    2. CO@Ken White Thanks for your answer. My first question specifically asks about re-using an existing icon. No hijacking, just sending a displayable **TEXT** message. There shouldn't be any security risk associated, as sending text-to-be-displayed to my own icon or to another icon should result in exactly the same. Unless you can explain otherwise, of course.
      singulars
    3. COSorry. Misunderstood your question somewhat; it's still not going to work, though, as the docs specifically state. There are only a couple of ways to pass text between apps safely (since the text is actually a character pointer), and notifications are not included in those ways. I don't understand the desire to avoid adding an icon, however, since that is *exactly* how they're designed to be used even for short purposes (as noted in the last sentence of your docs quote above).
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload