What steps will reproduce the problem?
1. Create a task to find player name "[clan tag]$" to search for clan members
2. Set to multiple (not single, or destroy)
3. Add a message/notification when player is found
4. Run task; it will endlessly run, finding the first match, showing a message,
finding the first match, showing a message, and so-on endlessly spamming
messages and preventing the user from killing the task.
What is the expected output? What do you see instead?
I assumed it would repeat to find *each match* to the player name query and
show which server(s) the player(s) were on. Instead, it spammed notifications
for the first match endlessly. I have to force the program to end, turn off my
network (to prevent the possibility of the task finding any results), and then
re-open urtconnector to delete the task before turning the network back on.
What version of the product are you using? On what operating system?
0.9.0 on Windows 8 (Sorry for the lack of detail, I'm booted into Mac OS X at
the moment!)
Please provide any additional information below.
Maybe allow for multiple results in a search like this, OR detect and deny
creation of such an infinite loop in tasks. At the very least, add spam
protection to prevent the app from creating so many notifications for the same
thing in an instant. When spam protection is triggered, ask to delete or edit
the task. Just some ideas.
Original issue reported on code.google.com by iyn...@gmail.com on 24 Aug 2013 at 4:14
Original issue reported on code.google.com by
iyn...@gmail.comon 24 Aug 2013 at 4:14