Heya, SLRB. What you're seeing isn't a bug, but maybe not optimal screen use. If you look at the Display Settings, you will see that you can define two columns of expanded view information. Whether you are using it or not, AT2 reserves the screen area where the second column would be drawn. So the area I marked in orange in a modified version of your screen shot, is that reserved area, plus padding/margin area. That explains the orphaned column headings when you scroll far right. AT2 tries to show you the headers, even if the underlying columns are hidden. [Reservedspace](//muut.com/u/aeontimeline/s2/:aeontimeline:w5K8:reservedspace.png.jpg)
razyr - Could you explain what you mean by the display settings reference?
Sure. If you hit the Display button, you get access to a Display Settings dialogue. This lets you determine what extra information you want to show when you expand an event. It let's you define two columns of information, just by dragging the boxes around in the Settings dialogue. Stuff on the right side of the box goes in that orange box area that I drew when you expand events. Unfortunately, even when not expanded and even if you don't have any items in that second column, the program still reserves a big hunk of real estate - just in case you change your mind in the future, maybe?
Ah - got it. Thanks.
I think this is on the list of things that Matt is going to look at after the IOS version ships and they revisit the queue of yummy stuff we're trying to coax, cajole and/or coerce him to do in the next release.
Thanx...I appreciate the explanation. To Matt et al...Adding this explanatory info to the users' guide would help, if there is no time to address a full code fix given other priorities. I find the effect pretty hostile from a user interface confidence POV. Perhaps a quick temporary tweak so the effect is less confusing is to shade and outline the space reserved for display info...then one could see the relationship info disappear behind the display box as the scroll bar is moved. Not a great tweak, but perhaps better than the current limited (for me anyway) visual queue that info is being masked. Changing topics...anybody have a sense of when the IOS version will ship, so we can get on with the coaxing and cajoling (grin).
Hi, Thanks for the discussion. The representation of this space is cleaner in our upcoming iOS version, and we would expect to roll that neater design across to the Desktop version in the future also. It still uses a fixed width for all events (because the alternative is awkward), but the delineation is clearer between the two areas. The iOS version has gone out to private beta testers now, and barring any major bug discoveries, will be released before the end of the year. Jess