Existing users, 
From schisaproductions:
Below are responses to recent feedback which I appreciate.
quali:
1) The crashes are disturbing to me: I would like to hear from you (and anyone with crashes) if it isn't a bother so I can track down what's going on (e.g. crash log text for FTLCtimelines from Library > CrashReporter folder as viewable in Console program). I haven't had any such crashes in development in a while so I need to be able to get a handle on what's what with it.
2) I'll look into exporting images to the native formats. As it stands, the thing that comes to my mind is copy&pasting the images into a program that does allow the creation of these files, but perhaps I'm incorrect.
3) This is the first time I've heard of HEML and I'm going to study said format since it seems to be relevant to FTLC (thanks for the link).
LVWolfman:
1) The remark about dialog box buttons ("I'll shift the date") I consider, perhaps incorrectly, a subset of the issue of language localization (other than English) which I've not had the time to deal with.
2) I agree with the length of fields remark, would prefer maybe a "..." within long record names when appropriate (e.g "LLLLLongName" to "LLL....Name"). Hope to get around to this and other limitations in the program.
3) Regarding a Windows version, I'd like to do so, but my current circumstances provide no easy access to a Windows based computer on which to test the thing.
FTLCtimelines
timeline making tool
Version: 0.9.6.1.00
response from schisaproductions
Feedback Type: Commentary
Contributed by: aPelican Friday, November 07 2003 @ 09:03 AM PST
Product Platform: MacOSX
Used Product For: Six Months
Comments
response from schisaproductions - aPelican
Thanks for the crash log. I would have gotten back to you sooner, but I've neglected to view these comments. The ATSUSetFontFallbacks messages leads me to suspect some font initialization trouble with FTLC (perhaps relying on the wrong information from the OS about fonts); i don't experience the crash, which makes me suspect the above again. In the most recent update, I've changed the way said initialization takes place, and if the update is (or is not) still crashing for you, assuming you still bother to download it, let me know if it's no trouble.Tuesday, November 25 2003 @ 08:02 AM PST
response from schisaproductions - quali
Also, when I mentioned native pdf, eps, or ps formats, I should have probably said any native vector graphic format. The heart of this comment relates to the readability difference between the two formats (vector vs. bitmap) when it comes to using timelines for display purposes, in printed material for publication, etc. I am a firm believer that using a Mac allows me to achieve very professional publication material in very simple ways. To this end, I would like to see the output files available in crisp, clean, ready to print and manipulate vector based formats.
Saturday, November 08 2003 @ 10:50 AM PST
response from schisaproductions - aPelican
Concerning native pdf, etc. While FTLC has employed vector graphics for all timeline(and circle) graphics since a few updates ago, I assume that printing and then saving the print as a PDF file (standard OS X print) isn't creating the quality you require (I don't know how the OS handles an applications pics under these circumstances, but I am guessing it treats pics as pics and does not generate raw PDF data for them even if they are vector based pics). Though I don't have a postscript printer, it seems the tools are available to create raw PDF data in FTLC: but I don't think this will be a simple task (requires self education, testing, etc.), so- assuming I get to it -I don't expect any implementation of it too soon.And... regarding HEML. I've connected with those who run it, but haven't had a few questions answered from them. I've seen what it can do and think it would be useful to interact with HEML. Would be easier to import from HEML than to export to HEML (for importing, one can pick and choose what info one wants from a file, for exporting, one has to comply with format specifications).
Anyway, I continue to give thought to these matters, but nothing more at this point.
Tuesday, November 25 2003 @ 08:04 AM PST
response from schisaproductions - quali
This is directly copied from the system.log file after the crash in Panther on a iMac Special Edition 400 MHz PowerPC G3 with 384 MB of SDRAM:
Nov 8 12:19:41 localhost /Users/quali/Desktop/FTLCtimelinesXfolder.1/FtlcTimeLines(X): *** Warning: ATSUSetFontFallbacks has been deprecated. Use ATSUFontFallbacks objects instead. *** Nov 8 12:19:55 localhost crashdump: Started writing crash report to: /Users/quali/Library/Logs/CrashReporter/FtlcTimeLines(X).crash.log Nov 8 12:19:55 localhost crashdump: Finished writing crash report to: /Users/quali/Library/Logs/CrashReporter/FtlcTimeLines(X).crash.logThis came out of the FtlcTimeLines(X).crash.log file:
Date/Time: 2003-11-08 12:19:52 -0600 OS Version: 10.3 (Build 7B85) Command: FtlcTimeLines(X) (/Users/quali/Desktop/FTLCtimelinesXfolder.1/FtlcTimeLines(X)) PID: 374 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0000001c Thread 0 Crashed: #0 0x004c1728 in 0x4c1728 #1 0x004c566c in 0x4c566c #2 0x020a63cc in 0x20a63cc #3 0x0202c06c in 0x202c06c #4 0x02052afc in 0x2052afc #5 0x0201b3a8 in 0x201b3a8 #6 0x027198dc in 0x27198dc #7 0x026d2abc in 0x26d2abc #8 0x026c87f4 in 0x26c87f4 #9 0x026c863c in 0x26c863c #10 0x026c85cc in 0x26c85cc #11 0x0276562c in 0x276562c #12 0x026df538 in 0x26df538 #13 0x0279ff28 in 0x279ff28 #14 0x0273c3ac in 0x273c3ac #15 0x0273bd28 in 0x273bd28 #16 0x0273a110 in 0x273a110 #17 0x0273a290 in 0x273a290 #18 0x027385ec in 0x27385ec #19 0x021cd634 in 0x21cd634 #20 0x02736ae0 in 0x2736ae0 #21 0x02736a48 in 0x2736a48 #22 0x0263a778 in 0x263a778 #23 0x02009318 in 0x2009318 #24 0x902da4d4 in CCFM_LaunchApplication (CCFM_LaunchApplication + 468) #25 0x00008840 in main (main + 360) #26 0x00008408 in _start (_start + 392) #27 0x0000827c in start (start + 48) PPC Thread State: srr0: 0x004c1728 srr1: 0x0000f030 vrsave: 0x00000000 cr: 0x44002228 xer: 0x0000000a lr: 0x004c566c ctr: 0x004c55d0 r0: 0x004c566c r1: 0xbfffe4e0 r2: 0x000f7000 r3: 0x0000001c r4: 0x000f8bf8 r5: 0x004a9858 r6: 0x00000030 r7: 0x0072490c r8: 0x00000002 r9: 0x00000008 r10: 0x00000003 r11: 0x00000974 r12: 0x000f7ac0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000 r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000 r20: 0xbffffe70 r21: 0xffffffff r22: 0xbffffc20 r23: 0x00000000 r24: 0x0036fe28 r25: 0x000f8bf8 r26: 0x00000001 r27: 0x01bff548 r28: 0x0000001c r29: 0x000f9320 r30: 0x01bff52c r31: 0x0000001cHope this is helpful.
Reply to This
Saturday, November 08 2003 @ 10:35 AM PST