profileevents() and order of event nodes under project/exec/events

I just wonder if there is a reason why the events are not sorted by the event time in the event list (project/exec/events). Seems to be that they are ordered in creation time, which depends on the position of the object in the tree, etc., right?
The command profileevents() is just a print out of this tree and his information, right?

Am I right, that the only way to figure out when will be the next event is to search through the event list with eventget(n,2) where the second parameter 2 means to look for the event time.

Is there a reason why the event list is not sorted by the time?
Otherwise it would be very easy to figure out when the next event will happen by just using eventget(1,2).

Or would it be an idea to have a command called nexteventtime() to get this time?
Or having a command called nexteventnode() to pointer on the next event node and be able with eventget() to get the time and other information?

Thanks in advance for some information.
tom the (A)tom

Hi Tom,

As far as I know, the current method of sorting the events is much faster then the old sorting where you could see the sequence of all events. I used this also to see what was happening in my model.
The next event is always the first one in the list.
I think it would be a good idea to change the function profileevents(), so that the events are sorted when printed. Speed is no issue here.. and you can see the real sequence of the events.

Tom,
The eventlist is implemented as a heap sort. This means it uses a partially ordered tree to sort the list, instead of a fully ordered tree. Lolke is right that the first event in the list is always the next event to happen. The partially ordered tree is structured such that event 1 comes before events 2 and 3, but there's not any ordered relationship between 2 and 3. Event 2 comes before events 4 and 5, event 3 comes before events 6 and 7, and so on; basically, event x will always be before event x*2 and event x*2+1. By doing this, it significantly decreases the number of checks that need to be made to put a new event into the list and to take an event out of the list.

I agree that there needs to be some command to fully sort the list, and profileevents should call that command before printing the events out. This has been put on the development list.

Lolke,
Anthony,

Thanks for your replies. The most important information for me was that the first event in the list is the next event which will happen.
So with eventget(1,2) I get the time when the next event will happen. That was what I was looking for.
Thanks Guys and thanks that in the future we will get some commands to sort the list. That’s just great.