0.5 glitches and a COQ

User avatar
Spitfire31
Posts: 242
Joined: Sun Oct 01, 2006 8:11 pm
Location: Sweden

Mon Jan 10, 2011 2:49 am Post

Hi Matt,

Thank you so much for Aeon TL 05! The new timeline design with the Cmd-wheel zooming is just great. Very easy to grasp and manipulate.

Having only tested briefly with a new file, I've found some stuff. I'm on a MB Pro, 10.5.8

1) When entering Timeline Settings, typing data in the date fields doesn't seem to register as changes, while using the up/down arrows does.

2) If I set a timeline range in Timeline Settings (e.g. 1920–2011) and zoom all the way out, the respective end points become 1911 and 2021 respectively. A bit confusing – or is it intended, to provide a margin of safety?

3) The status bar at the bottom doesn't seem properly connected in the current build. In the above example (timeline range 1920–2011) its scale runs from 1501–2101 and the marked range is from about 1898–1980…

4) It would be nice if the timeline zoom level and position could be remembered when saving/opening files. Currently, the file opens at the maximum resolution, whereas the saved, or at least the minimum, resolution (to give an immediate overview on opening) would seem to be more helpful.

5) I consistently get COQs – Thread 0 crashing with the below result.

Again, thank you for all the great work you have put into this release. It bears promises of a very slick and highly useful app, especially considering your roadmap.

Best regards,

Joachim

---

Process: Aeon Timeline [49147]
Path: /Applications/Aeon Timeline.app/Contents/MacOS/Aeon Timeline
Identifier: com.aeon.timeline
Version: 0.5.0 (0.5.0.0)
Code Type: X86 (Native)
Parent Process: launchd [75]

Interval Since Last Report: 578849 sec
Crashes Since Last Report: 7
Per-App Interval Since Last Report: 1145 sec
Per-App Crashes Since Last Report: 3

Date/Time: 2011-01-10 03:35:03.784 +0100
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: 60653A6C-864E-4BA7-858D-5FB64A684621

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Crashed Thread: 0

Application Specific Information:
objc[49147]: FREED(id): message scrollNotificationViewContentBoundsDidChange: sent to freed object=0x16f4eb60

Thread 0 Crashed:
0 libobjc.A.dylib 0x96571bfa _objc_error + 116
1 libobjc.A.dylib 0x96571c30 __objc_error + 52
2 libobjc.A.dylib 0x96570637 _freedHandler + 58
3 com.apple.Foundation 0x9711742a _nsnote_callback + 106
4 com.apple.CoreFoundation 0x90b3e47a __CFXNotificationPost + 362
5 com.apple.CoreFoundation 0x90b3e753 _CFXNotificationPostNotification + 179
6 com.apple.Foundation 0x97114680 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
7 com.apple.Foundation 0x9711ded8 -[NSNotificationCenter postNotificationName:object:] + 56
8 com.apple.AppKit 0x976c8024 -[NSView _postBoundsChangeNotification] + 167
9 com.apple.AppKit 0x976c7ef7 -[NSView setBoundsOrigin:] + 524
10 com.apple.AppKit 0x976c7cce -[NSClipView setBoundsOrigin:] + 68
11 com.apple.AppKit 0x976c6d05 -[NSClipView setDocumentView:] + 518
12 com.apple.AppKit 0x9769964e -[NSView _removeSubview:] + 43
13 com.apple.AppKit 0x9768f3d1 -[NSView _setSuperview:] + 667
14 com.apple.AppKit 0x97698f86 -[NSView removeFromSuperview] + 338
15 com.apple.AppKit 0x97712695 -[NSView removeFromSuperviewWithoutNeedingDisplay] + 46
16 com.apple.CoreFoundation 0x90aec676 CFArrayApplyFunction + 198
17 com.apple.AppKit 0x976a5adc -[NSView _finalizeWithReferenceCounting] + 712
18 com.apple.AppKit 0x976a57e8 -[NSView dealloc] + 46
19 com.apple.AppKit 0x977f0e39 -[NSClipView dealloc] + 147
20 com.apple.Foundation 0x9711344f NSPopAutoreleasePool + 431
21 com.apple.Foundation 0x9711db22 +[NSAutoreleasePool releaseAllPools] + 50
22 com.apple.AppKit 0x97861637 -[NSApplication _deallocHardCore:] + 505
23 com.apple.AppKit 0x9786030d -[NSApplication terminate:] + 742
24 com.apple.AppKit 0x97780e8f -[NSApplication sendAction:to:from:] + 112
25 com.apple.AppKit 0x9782fb64 -[NSMenu performActionForItemAtIndex:] + 493
26 com.apple.AppKit 0x9782f869 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 220
27 com.apple.AppKit 0x9782f4ef -[NSMenu performKeyEquivalent:] + 866
28 com.apple.AppKit 0x9782dd94 -[NSApplication _handleKeyEquivalent:] + 492
29 com.apple.AppKit 0x9774aac7 -[NSApplication sendEvent:] + 3997
30 com.apple.AppKit 0x976a7fe7 -[NSApplication run] + 867
31 com.apple.AppKit 0x976751d8 NSApplicationMain + 574
32 com.aeon.timeline 0x00002105 _start + 208
33 com.aeon.timeline 0x00002034 start + 40

Thread 1:
etc.

ma
matt
Posts: 1180
Joined: Mon Jul 30, 2007 9:35 am

Mon Jan 10, 2011 4:27 am Post

Hi,
1) If you hit Enter, it should become typable. I thought it was setup to type by default, but perhaps I am wrong with that. I will play around with it and make sure it behaves correctly tabbing in and out, and clicking in a field directly.

2) This is done intentionally - it decides how often it wants to place the Major tick marks, and then displays the one immediately before the start and immediately after the end. So if you are seeing 10 year intervals, it will display exactly as you suggest. If you zoom in to 5 year intervals, it will show 1916 and 2016. If you zoom in to 1 year intervals, it will show1920 - 2011 as you have set it.

In other words, your start and end date are preserved (unless you drag an event outside that bounds), but the display will adapt depending on where your tick marks are placed on the timeline.

3) See the other thread regarding the bug when first starting up. Is the problem in Story Arc mode or Entity Mode? If you swap to Story Arc mode, then back to Entity Mode, does it then resolve itself and make sense? The Context Bar should show a range that is approximately 10 times the one in the main view, and the highlighted region should be pretty exact.

4) The code is already there to do it, but perhaps it isn't working (you do have to save the file for it to reopen at that zoom). I will check again tonight to see if there is a bug here.

5) Thanks for the stack trace. Is COQ crash on quit? Looks like I need to tell myself off for some sloppy closing somewhere.

Thanks,
Matt

User avatar
Spitfire31
Posts: 242
Joined: Sun Oct 01, 2006 8:11 pm
Location: Sweden

Mon Jan 10, 2011 5:21 am Post

Hi Matt,

Thanks for the fast feedback.

matt wrote:1) If you hit Enter, it should become typable. I thought it was setup to type by default, but perhaps I am wrong with that. I will play around with it and make sure it behaves correctly tabbing in and out, and clicking in a field directly.

It is typeable, that wasn't my gotcha. What threw me was that I thought that the typed value would stick if I clicked anywhere else in the windows, like in some programs. Delving deeper, I found that I have to confirm by either hitting Enter or clicking in some other field, not just anywhere. No biggie…

matt wrote: 2) This is done intentionally - it decides how often it wants to place the Major tick marks, and then displays the one immediately before the start and immediately after the end. So if you are seeing 10 year intervals, it will display exactly as you suggest. If you zoom in to 5 year intervals, it will show 1916 and 2016. If you zoom in to 1 year intervals, it will show1920 - 2011 as you have set it.

In other words, your start and end date are preserved (unless you drag an event outside that bounds), but the display will adapt depending on where your tick marks are placed on the timeline.

Fine!

matt wrote: 3) See the other thread regarding the bug when first starting up. Is the problem in Story Arc mode or Entity Mode? If you swap to Story Arc mode, then back to Entity Mode, does it then resolve itself and make sense? The Context Bar should show a range that is approximately 10 times the one in the main view, and the highlighted region should be pretty exact.

Yes, switching to Story Arc and then back to Entity makes a lot more sense. Although it's a bit strange to see 1701 at the far left, at the minimum zoom setting…

matt wrote: 4) The code is already there to do it, but perhaps it isn't working (you do have to save the file for it to reopen at that zoom). I will check again tonight to see if there is a bug here.

It isn't working for me when opening a saved file.

matt wrote: 5) Thanks for the stack trace. Is COQ crash on quit? Looks like I need to tell myself off for some sloppy closing somewhere.

Yes, that's Crash On Quit. Sorry for the shorthand… ;-) I just noticed that even closing a file (without quitting Aeon) will result in a similar crash.

Best,

Joachim

ma
matt
Posts: 1180
Joined: Mon Jul 30, 2007 9:35 am

Thu Jan 13, 2011 1:42 pm Post

Hi Joachim,
The just-released 0.5.1 version should hopefully fix your crashes, and make it so you don't have to move to a new field for your date changes to hold when adding events.

Zoom level should save/open properly now too.

Please let me know if any of these problems persist.

Matt

User avatar
Spitfire31
Posts: 242
Joined: Sun Oct 01, 2006 8:11 pm
Location: Sweden

Fri Jan 14, 2011 6:45 am Post

matt wrote:Hi Joachim,
The just-released 0.5.1 version should hopefully fix your crashes, and make it so you don't have to move to a new field for your date changes to hold when adding events.

Check on both!
matt wrote:Zoom level should save/open properly now too.

Check on that too.

Great work with fixing stuff in 0.5.1! TL is getting really useful now.

One small wish - it would perhaps be nice if Aeon started up with the latest file, even if you just launch the app (just like Scrivener, for instance)?

I'll dig deeper in the coming days.

Thanks again!

Joachim