How to reduce the number of Balloon

Question

I've got a Directory and a FileSystemWatcher and I want to reduce the number of Balloon.Show everytime I delete a file but how can I do? Because everytime I delete like 20 files explorer.exe crashes cause of the too ShowBalloonTips. There is a solution that I found in this forum that works if I delete the files one by one, but if I delete them all togheter it gets bugged and don't fire OnDelete no more... Any suggestion?

private void InitializeWatcher()
{
    watcher.NotifyFilter = NotifyFilters.LastAccess | NotifyFilters.LastWrite
                           | NotifyFilters.FileName | NotifyFilters.DirectoryName;
    watcher.Filter = "*.*";
    watcher.Changed += new FileSystemEventHandler(OnChanged);
    watcher.Created += new FileSystemEventHandler(OnCreated);
    watcher.Deleted += new FileSystemEventHandler(OnDeleted);
    watcher.Renamed += new RenamedEventHandler(OnRenamed);
    watcher.EnableRaisingEvents = true;
}

private void OnDeleted(object sender, FileSystemEventArgs e)
{
    SetBalloonTip("File Eliminato");
    notifyIcon1.ShowBalloonTip(1);

    ((FileSystemWatcher)sender).Deleted -= new FileSystemEventHandler(OnDeleted);
    timerRepeat.Interval = 500;
    timerRepeat.Elapsed += new ElapsedEventHandler(t_Elapsed);
    timerRepeat.Start();
    } 

  void t_Elapsed(object sender, ElapsedEventArgs e)
    {
        ((System.Timers.Timer)sender).Stop();
    }

score 0 · Answer 1 · answered Jun 29 '16 at 13:15

0

It's not the most efficient way, but I would probably hold the number of files deleted and show the tooltip every nth time, like

private int deleteCounter = 0;

private void OnDeleted(object sender, FileSystemEventArgs e)
{
    //your delete code
    if(deleteCounter % 50 == 0)
    {
        SetBalloonTip("File Eliminato");
        notifyIcon1.ShowBalloonTip(1);
    }
}

answered Jun 29 '16 at 13:15

Selim Balci

940
2
11
26

Even if I don't understand how this can work this actually works! Thank you buddie! P.S: Nop, my bad, this doesn't work at all – JoeSpastico Jun 29 '16 at 13:27
if this fixed your problem, please mark it as the answer. thank you. – Selim Balci Jun 29 '16 at 13:31
Well not, sorry : – JoeSpastico Jun 29 '16 at 13:34
Are you actually increasing the deleteCounter value by 1 each time you delete a file? Also, if this is still too fast, try changing the value of the dividing number. – Selim Balci Jun 29 '16 at 13:51
Well I added that but I don't really like it and with houndreds of file deleted even in that way would bug. – JoeSpastico Jun 29 '16 at 13:52

score 0 · Answer 2 · answered Jun 29 '16 at 17:24

You better wait a bit before you show the Notification and prevent to much notifications to be pushed on the explorer.

The best way to do this is by using your timer to delay the notification by 500 ms. During that time you keep track of how many files got deleted in a simple counter. Once the Timer ticks, you show the Notification with the number of files deleted so far. You reset the counter and wait a bit for the notification to disappear. Then you're back in the initial state and the process can restart.

An implementation of above scenario might look like this:

int pendingDeletes = 0;
int TipState = 0; // keeps the state of the notifyIcon, 
                  // 0 = initial,
                  // 1 is about to be shown
                  // above 1 is waiting to reset to 0

private void OnDeleted(object sender, FileSystemEventArgs e)
{
    pendingDeletes++;
    if (TipState == 0)
    {
        TipState++; 
        // it didn't want to start http://stackoverflow.com/a/18348878
        this.Invoke( new MethodInvoker( () => timer1.Start()));
    }

}

// tick every 500 ms
private void timer1_Tick(object sender, EventArgs e)
{
    Trace.WriteLine(TipState);
    switch(TipState)
    { 
        case 1:
            notifyIcon1.BalloonTipText = String.Format("{0} deleted file(s)", pendingDeletes);
            notifyIcon1.ShowBalloonTip(500);
            pendingDeletes = 0;
            TipState++;
            break;
        case 2:
            // do nothing
            TipState++;
            break;
        case 3:
            // maybe do something if pendingDeletes > 0
            timer1.Stop();
            // back to initial state
            TipState = 0;
            break;
        default:
            // prevent mishaps
            TipState = 0;
            break;
    }
}

I couldn't find a reliable way to detect if the notification is already gone, hence the extra wait states before I reset back to the initial state. If your users really care about the exact number of deleted files you might want to tighten the housekeeping around the number of deleted files reported. I leave that as an excercise.

Thanks so much man, but I already found a faster solution yesterday, but also your way is good! — JoeSpastico, Jun 30 '16 at 07:56

How to reduce the number of Balloon

2 Answers2