Enumeration Q.

Would it be possible to change the current Event enumeration of:

1

2

--3

--4

5

6

--7

8

Into something more useful like:

1

2

--2.1

--2.2

3

4

--4.1

5

Or even this:

1

2

--2.a

--2.b

3

Hope it's not just me that see it more organized/logical/useful.

I don't see how it would be that helpful. The event enumeration at the moment is useless for organisational purposes anyway, because adding an event in the middle of the sheet makes all the ones below get pushed back.

I came across this idea when I found myself in a long chain of events.

When I wanted to check in which sub event I'm currently in I looked at the numbers which revealed nothing.

I was not in the "main" chain of events but rather deep inside.

The indentation didn't help much so I had to scroll back up and compare the spaces between the event I was working on and an event which belonged to the "main" events.

If the enumeration was there I would have know I'm working on even number 14.3 (or 14.c) which than was pushed with the mouse to the main events place.

In the future when you'll click on event #14 all the 14.1 and 14.2... will be folded into event #14 leaving the next event at #15 (and not #32 for example).

Makes sense?

I like this idea. The current enumeration has no practical purpose.

I don't like this idea. Having worked regularly on an event sheet 10 levels deep with more than 5000 events, this might sound like a good idea in theory, but in practice for anything complex it would be an utter mess.

Letters would be right out because it wouldn't last more than 26 events. For each level, you'd have to add another point to it. So you'd get something crazy like event 1.2.3.4.5.6.7.8.9. It would be harder to read than what's currently implemented.

I think C2 should use what CC has, lines that show levels. Even better, I think they should be highlighted as well when an event in its level is selected, making it easier to spot which one you're supposed to be looking at.

Arima, In the case of 5,000 events you prefer this:

3012

-3013

--3014

---3015

---3016

----3017

Over this?

32

-32.1

--32.1.1

---32.1.1.1

---32.1.1.2

----32.1.1.2.1

The first has no meaning beside counting events. It has no purpose too beside telling someone he/she has an error on event #40,321.

Your highlight idea is a good start/direction but it lacks the point I was trying to make - a mechanism which will show you how deep your current event is.

You also forgot my prediction - events will be able to fold in the future. With my suggestion you won't see the mess you mentioned in the 1.2.3.4.5.6.7.8.9 scenario (have you really gone so deep?)

I would love to have it say 3.1 when i add a subevent to the third event on my sheet. I would prefer numbers over letters too though..

I second HotGods idea

I agree with Arima, many users use very deeply nested events and instead of being event 9, it could be event 3.1.1.2.1.1. Not only is that less helpful, it also is probably too wide to fit in the event sheet in its current design!

Perhaps sub-events could just be separately numbered 1, 2, 3... at each nesting level?

Imo, being able to colorize events at will (like set a color for all the events of a group) would be more helpful and meaningful than 1.2.3...

I only use the line numbers when telling someone on the forum what to modify and where. There's no other case I check those, especially when using groups.

Indent is really enough, alongside comments.

Arima, In the case of 5,000 events you prefer this:

3012

-3013

--3014

---3015

---3016

----3017

Over this?

32

-32.1

--32.1.1

---32.1.1.1

---32.1.1.2

----32.1.1.2.1

The first has no meaning beside counting events. It has no purpose too beside telling someone he/she has an error on event #40,321.

Your highlight idea is a good start/direction but it lacks the point I was trying to make - a mechanism which will show you how deep your current event is.

That's exactly what my idea is - the vertical lines CC has accomplish that in a much more elegant fashion IMO.

Honestly, I can't think of any reason to want to know how deep an event is. That information alone, without the context of the conditions in the events above it is pretty much useless to me. Using CC's vertical lines, I can tell what events are on what level. That system is a lot cleaner and works just fine. If the line of the currently selected event was highlighted, that would be even better.

You also forgot my prediction - events will be able to fold in the future. With my suggestion you won't see the mess you mentioned in the 1.2.3.4.5.6.7.8.9 scenario (have you really gone so deep?)

Even when sub event collapsing is implemented, I would still have to look at it when working with those events! That wouldn't make any difference.

Do I prefer event 1981 to event 5.16.2.1.2.2.5.1.1.6.1? Vastly! Much simpler, much smaller, less keys to press, less likely for a typo, easier to read, much easier and faster to process mentally. Tell me at a glance - which is higher in the event sheet, event 5.16.2.1.2.2.5.1.1.6.1 or event 5.16.2.1.2.5.1.1.6.1? Comparing event 1981 and event 1960 is far quicker and easier.

Perhaps sub-events could just be separately numbered 1, 2, 3... at each nesting level?

Ashley Not sure what you mean?

Yeah the current method with a contiguous number for each line is better imho. If you get an error, you're not going to care if the offending line is a subevent. All you're going to care about is where it is.

My issues are telling subevents apart, that little line doesn't help with a lot of events.

I mean what am I going to do, get the ruler out?

How about these?

<img src="http://www.Logofusion.com/att/GUI-1.jpg" border="0" />

Adding the "level lines" is fine, but in my eyes the third screen removing the purple color blocks isn't.

It is maybe just a matter of habits, but to me it helps identifying where I am in my code. Without it, I'm lost.

Also, even with "level lines", I'd keep the event numering as it has its use.

Idealy such display in the event sheet should be dealt with in a "customize event sheet display" dialog with checkboxes.

Each one could end up displaying the event sheets to its liking.