Author Topic: Events  (Read 1620 times)

Mahound

  • Sr. Member
  • ****
  • Posts: 394
  • THE ONLY time i get screwed is when i play poker!
    • View Profile
Events
« on: January 26, 2011, 12:38:04 PM »
Beta V 2.6.4

This is a suggestion which i think will make the sounds events a little bit easier.

Could  the settings be changed on the "omit" events section of the events tab  At the moment You have to select the event one by one too omit an event.

I would like to see

1) The events be, by default -  Be made active inactive

2) A button or link, so that you can either select all events or select several events. For example, the inbox on googlemail, when you can select all / several  messages.
The idea is that you can select more than one event and either make them active or inactive

4) But also when you make an event  and click OK the  you have to tick on the action to make it active. I would like to see, that when you create an event, it becomes active once you click ok

5) Have the events highlighted,so that you can see at a glance wether the events are active or inactive.


Hope this makes some sense

Jim
« Last Edit: January 26, 2011, 06:13:28 PM by Mahound »

Corey Cooper

  • Administrator
  • Hero Member
  • *****
  • Posts: 5427
    • View Profile
Re: Events
« Reply #1 on: January 27, 2011, 10:56:00 AM »
I moved this topic, just so you know, to the Beta Testing forum.

So I think there could be some good ideas here, but I'm confused by some.

1) The events be, by default -  Be made active inactive

So, you're saying that when a new Event is created, it should be "Omitted" by default, so the user must deliberately make the Event active by unchecking the "Omit" checkbox?

2) A button or link, so that you can either select all events or select several events. For example, the inbox on googlemail, when you can select all / several  messages.
The idea is that you can select more than one event and either make them active or inactive

I understand this and it's been on my radar for some time.  The reason I haven't touched this yet is, essentially, application consistency.  If I change the Events tab to work this way, I need to change all of the tabs to work this way.  I'm not going to do one without the others because it's confusing and the application needs to be as consistent as possible.  There are certainly other examples of inconsistency in the application, but I'm not going to consciously introduce another one.  As with most features ... I hope to get to it some day.

4) But also when you make an event  and click OK the  you have to tick on the action to make it active. I would like to see, that when you create an event, it becomes active once you click ok

This confuses me.  Isn't this the opposite of the first point (1)?

5) Have the events highlighted,so that you can see at a glance wether the events are active or inactive.

The events are already highlighted in red text if they have an issue, such as having no Actions attached to them, or referencing Sounds that cannot be found on the disk.  I'm hesitant to introduce another highlight, but I do see the point.  How about the description of the event having a line through it, like this, if the Event is currently omitted (inactive)?

Mahound

  • Sr. Member
  • ****
  • Posts: 394
  • THE ONLY time i get screwed is when i play poker!
    • View Profile
Re: Events
« Reply #2 on: January 27, 2011, 05:08:22 PM »
Apologies for posting in the wrong thread. :D

 1 & 2)Yes! omitted by default.  Then I think it would be easier to tick the buttons and make an event active. I know that you could have a lot of events on there and that is why i suggested having one button to either select or deselect all

4) It confused me too when i reread it back. I hope this is a better explanation of what i meant.
When you make a new event, then a new action, you have to tick the box to make the action perform. Make a second action, such as a message  you have to tick that event too.  Then you click OK . Event created. and active What i was meaning was that the actions be active  but make the event itself, in-active . So that would tie in with what i meant in (1)

5)  Yes. your right about the highlighting,. daft idea.  but the line through the  description of an event if it is Omitted would be great.

Sorry if it seemed a bit confused, hope this was better explained

Jim


Corey Cooper

  • Administrator
  • Hero Member
  • *****
  • Posts: 5427
    • View Profile
Re: Events
« Reply #3 on: January 27, 2011, 05:33:06 PM »
Apologies for posting in the wrong thread. :D

 1 & 2)Yes! omitted by default.  Then I think it would be easier to tick the buttons and make an event active. I know that you could have a lot of events on there and that is why i suggested having one button to either select or deselect all

I'll have to think about whether or not I want to change the behavior at this point.  I think if I changed the Omit column to "Active" so that the checkbox had to be checked to make the event active, and unchecked to make it inactive, that would be a little confusing (inverting the current behavior).  Also, if a newly created Event started out as Inactive (or Omitted), that might also confuse someone - especially someone new to creating Events.

4) It confused me too when i reread it back. I hope this is a better explanation of what i meant.
When you make a new event, then a new action, you have to tick the box to make the action perform. Make a second action, such as a message  you have to tick that event too.  Then you click OK . Event created. and active What i was meaning was that the actions be active  but make the event itself, in-active . So that would tie in with what i meant in (1)

OK, this sounds like confusion about the "Perform" column, which is actually "Performed".  This checkbox does not tell the software which actions to perform and which not to perform.  This checkbox is a flag for whether or not the action has already been performed.  It's actually an internal flag that I exposed so the user could have more control over how the actions are performed.  So, when an Event fires and an action is performed, that flag (checkbox) gets set.  Then, the next time the Event fires the software knows which actions have already been performed so it can choose another (based on that Event's settings).  For example, if you had 3 different audio files for a player busting out, you could have one bust-out Event with 3 actions, one for each audio file.  The Event's settings could be to perform the actions in order.  The first player to bust-out would hear audio file 1 (and the "Performed" checkbox for the action that plays audio file 1 will get checked automatically by the software).  The second player would hear audio file 2.  And the third would hear audio file 3.  If after the second player was busted out you decided you like that audio file so much you wanted the third player to hear it, too, you could uncheck the "Performed" flag for the second action.

5)  Yes. your right about the highlighting,. daft idea.  but the line through the  description of an event if it is Omitted would be great.

I don't think it's a bad idea at all, it's just about balancing everything...  Might make sense to highlight the Event in red if it is currently Omitted, and maybe put an indicator next to it (like a "caution" triangle - or something like that) if the Event has a problem, like a missing audio file.