Author Topic: "Tagging" popup is really persistent  (Read 2583 times)

jporkkahtc

  • Senior Community Member
  • Posts: 1962
  • Hero Points: 185
  • Text
"Tagging" popup is really persistent
« on: August 08, 2011, 06:27:45 pm »
I keep getting a popup notification (Slick 16.0.1, Windows)
   Tagging
   The .NET libraries have not been tagged yet. To do that now, click here
This is really annoying, and I've not found a way to turn it off.
It flickers on and off frequently even when Slick edit isn't in the foreground.
#1: I don't care about .NET
#2: Even if I did, I should be able to close this and have it go away
#3: It messes with keyboard focus - making it impossible to type entries in dialogs like Find. (Dialog loses focus briefly, then gets it back. Text in the edit box is selected when the dialog gets focus, and the next keystroke then replaces all the text....).

I've even set "Disable all pop-ups", and this thing persists in bothering me.

jporkkahtc

  • Senior Community Member
  • Posts: 1962
  • Hero Points: 185
  • Text
Re: "Tagging" popup is really persistent
« Reply #1 on: August 10, 2011, 06:08:02 pm »
OK, so I solved this by editing CUTIL.e
In AddDotNetTagFile()
         _str msg = 'The .NET libraries have not been tagged yet.
To do that now, click <a href="<<cmd gui-make-tags">here[/url].';
         //_ActivateAlert(ALERT_GRP_WARNING_ALERTS, ALERT_SYMBOL_NOT_FOUND, msg, "Tagging", 1); // JPORKKA REMOVED!

I removed the call to _ActivateAlert().

This seems to be caused because I do not have .NET libraries installed, and Slick gets upset.
In a test here, I found it called this function 167 times when starting Slick!

It appears then that Slick keeps track and tries to display that toast 167 times, and takes quite a while to do so.

Jerm_jp

  • Community Member
  • Posts: 42
  • Hero Points: 0
Re: "Tagging" popup is really persistent
« Reply #2 on: August 11, 2011, 01:02:56 am »
I too was really annoyed by this, thank you for posting the question and most importantly, for posting a follow-up about how you bypassed this behavior.