search

ChrisS85 / 7plus

Automatically exported from code.google.com/p/7plus
2 stars 0 forks source link

Condition/Action Lists/Links #304

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
There is much redundancy in the condition/action setup. It might be a good idea 
to reuse conditions and possibly actions. This would obviously need much 
thought and I'm not sure if it's really a good idea. __Get, __Set and __Call 
may be of good use here to relay some things to the original condition/action 
list.

This would make it easier for the user to configure exclusion lists at the cost 
of additional event complexity. Another, possibly better idea might be to add 
OR operators to the condition list, and possibly allowing more than one trigger 
per event.

Original issue reported on code.google.com by fragman@gmail.com on 6 Jun 2011 at 1:10

GoogleCodeExporter commented 9 years ago 
Redesigning the event edit window might be a good idea to allow faster editing. 
The idea would be to keep the tabs above, add a trigger list and move the edit 
trigger/condition/action windows inside the same window to remove one level of 
windows.

Original comment by fragman@gmail.com on 6 Jun 2011 at 1:12

GoogleCodeExporter commented 9 years ago

Original comment by fragman@gmail.com on 6 Jun 2011 at 4:50

GoogleCodeExporter commented 9 years ago

Original comment by fragman@gmail.com on 6 Jun 2011 at 7:05

GoogleCodeExporter commented 9 years ago 
Event window is mostly redesigned now. There are a couple of smaller bugs left, 
but it's basically working. I think I'm not going to do condition/action lists 
anytime soon, supporting multiple triggers per event and/or OR operators for 
conditions is more useful and likely.

Original comment by fragman@gmail.com on 7 Jun 2011 at 7:05

GoogleCodeExporter commented 9 years ago

Original comment by fragman@gmail.com on 4 Jun 2012 at 3:37