All the labels in my trigger editor are duplicated so it takes me more time to find things in various categories. It's very frustrating and annoying. Anyone know how to solve it?
Ive had this happen before, no clue what causes it. It does seem to resolve itself though because our team's map was doing it for a while and then it went away.
I'm having this issue too, and I think it's screwing up my maps as well. I notice when I View Script from the Triggers Editor I see that it's including its native libraries 3 times as shown below:
I can deal with have duplicate labels, but it seems like my projects are showing errors that suggest that its having problems initializing the map.
If no one has any answers we should at least keep this thread alive and populated so that we can bring it to Blizzard's attention. It might be the cause of any of the current BNet issues as well.
this happened to me when i switched to windows 7, to be honest i didnt even notice until now that the issue was gone, so im guessing you just have to wait until it fixed itself
All the labels in my trigger editor are duplicated so it takes me more time to find things in various categories. It's very frustrating and annoying. Anyone know how to solve it?
Ive had this happen before, no clue what causes it. It does seem to resolve itself though because our team's map was doing it for a while and then it went away.
I'm having this issue too, and I think it's screwing up my maps as well. I notice when I View Script from the Triggers Editor I see that it's including its native libraries 3 times as shown below:
I can deal with have duplicate labels, but it seems like my projects are showing errors that suggest that its having problems initializing the map.
If no one has any answers we should at least keep this thread alive and populated so that we can bring it to Blizzard's attention. It might be the cause of any of the current BNet issues as well.
Oops, no wait, the error I was receiving was my fault. Still, this is a really annoying bug, and needs to be fixed.
@redpand: Go
this happened to me when i switched to windows 7, to be honest i didnt even notice until now that the issue was gone, so im guessing you just have to wait until it fixed itself
So, nobody knows how to solve this bug? I still experience it.
Well if it still occurs, I had the same problem but fixed it today with Blizzard's repair tool.
Weird bug anyway