Hi Paul, We made the decision to change the colour selection for better compatibility with our iOS app. Because the Desktop and iOS apps can have different skins, we chose a smaller range that will work well across all of the different themes. We also adjust them slightly per theme to make them a little more visible when required, which we couldn't do if we allowed a user to pick from all colours. That second one is definitely a bug. I will look into it straight away, and see if I can get out a fix. Although you won't be able to undo it in the new file, a backup of your original file still exists, so as soon as I fix the bug you will be able to open the original "aeon2" file again and have it reconverted to the new format. I will get back to you shortly regarding a timing estimate on fixing the bug. Are you on Mac or Windows, out of interest?
I will have an update available for direct Mac/Windows customers within the hour, and for App Store customers as soon as it clears review.
Hi Paul, The fix for the second of these issues (link titles) has now been released if you are a direct customer., and is awaiting approval from Apple for the App Store release. Although we don't intend to go back to a free-form colour picker, we can certainly look to expand the range of available colours. It is very difficult to come up with a range of colours much larger than the current one without having a high degree of similarity between certain colours, so I had hoped that the group provided would be sufficient for everyone's needs. Even within our current set I feel like a few are quite close together as it is. Could you perhaps provide some examples of colours that you were using in the past that you feel are not represented now?
Hello Matt, Thanks for the the fix for the link titles. I'm impressed & appreciative of the quick response, which allows me to restore from a backup without losing a significant amount of work. Regarding colours, it _is_ hard to find distinctive ones, which is why I spent a fair amount of time on the set I use. Here's a screenshot from my project: [Screen Shot 2018-05-02 at 10](screenshot20180502at10.08.33pm.png) You can see that the greens, in particular are similar—but you can see why I wan't them all to be green too. I hope I can say this without seeming offensive, but why should the developer care if the end user chooses colours that are similar, or clash, or commit any other aesthetic crime? Why _not_ include a freeform colour picker? How about using Apple's baked-in palettes, or your own version of same, which combine pre-defined sets of colours with an option to ignore them and pick your own? [Screen Shot 2018-05-03 at 7](screenshot20180503at7.33.22am. png) [Screen Shot 2018-05-03 at 7](screenshot20180503at7.54.08am.png) (These are from TextEdit, but it's the standard Mac approach.) Thanks for your time & consideration.
Not sure where my screenshots went. Trying again: [Project legend](//muut.com/u/aeontimeline/s2/:aeontimeline:PKaA:projectlegend.png.jpg) [Colour picker 1](//muut.com/u/aeontimeline/s1/:aeontimeline:c5KR:colourpicker1.png.jpg) [Colour picker 2](//muut.com/u/aeontimeline/s1/:aeontimeline:fpcN:colourpicker2.png.jpg)
Sorry—didn't see your other question. I'm using a Mac, if it isn't already obvious.
Hi Paul, If possible, could you send me a timeline with your old colour scheme? If you wish for your data to remain confidential, you can make a copy and delete all of the events and entities in the timeline before sending it to me (make sure you do this in version 2.2). I will take a look at that relative to our own new colour samples. If you are able to, email the file through to firstname.lastname@example.org and reference back to this thread so I know what the file is for :-) Matt
I'll send you a file. Please just delete it thoroughly when you're done with it.
Hi Matt, I'm dismayed by the loss of color options. I have multiple gradations for various atmospheres, which, as you can imagine, are almost infinite in range. With only a few colors, this feature is sorely reduced in value. Although I understand the bases for the revision, the visuals are now pointless. I am wondering if there is way to offer one template style that is designed to retain an wide array of colors, if users understand that they array would not show across platforms but would be preserved once the project is reloaded on computer (after opening in, e.g., ipad). Thanks!
I second this suggestion. For background, I've spent the past couple of years building a timeline that contains close to a thousand events, hundreds of external links, and many dozens of entities. AT has completely revolutionized the way I do research for writing fiction novels. Prior to this update, it was the perfect tool for my needs. Pretty much the greatest thing since sliced bread. Discovering AT was like finding a missing piece of my writing process-- something I'd needed for years without realizing it. But... I don't have an iPad, and I won't be getting one in the foreseeable future. Plus, I'd never ever try to work on this enormous timeline on my dinky little phone. And NONE of the sweeping changes listed to enable iOS support sound the least bit appealing or helpful to my use case. In fact they all sound detrimental, like dramatically limiting the color palette. I put a LOT of thought, experimentation, and trial and error into my customizations. The color set I devised for this project is deeply embedded in my brain now. So now I feel like I'm stuck betw een a rock and a hard place. My choices are: (1) stay up to date, but accept a bunch of changes that I don't need, don't want, and which run the risk of severely degrading all the work I've done over the past couple of years, or (2) freeze my version of AT at 2.2.x and run all the risks that come with running out-of-date, unsupported software. I honestly don't know what to do now. I understand the business case for widening the customer base. But desktops and laptops aren't dead and I really wish that software developers would stop acting like they are. Not everybody WANTS to work on iOS devices. Let the iOS people opt in to the limitations of their chosen platform, rather than forcing everybody else to opt out by running older versions of AT.
Just chipping in again to agree with the previous contributors. Do what other software companies do, _please_: Give a palette of "safe" colors for people designing for iOS. If necessary, give several palettes, to suit different themes—but also give us the freedom to choose for ourselves if we need or just want to. Apparently I'm not the only one to really feel the bite from losing that option.
And one more thought, following up: People who want to see their work on multiple platforms, either for their own use or, especially, for viewing by others, have some responsibility to do some checking for themselves that all aspects, including colour, look OK. Treat your users as grown-ups.
Hi all, Thanks for the feedback. I will look to increase the colour options in the next minor update. There are a couple of technical implementation issues involved beyond matching the themes, so it is unlikely to revert back to complete freedom to choose any colour, but I will increase the range to provide better granularity within colour ranges etc. Matt
Hi, Just letting you know, that the latest update is available with a wider range of colours available. Jess
Thank you for being so receptive and responsive to user feedback!
Belated thanks from me for the improved colour choices. Looks like I can live with the new selection.
Wow. More colors? Already? Can you please manage my life? This is so unfamiliar; I didn't even have time to forget about this; to remember it again; to grumble; and to experience the awful frustration of knowing my wee small voice flew into the ether in a silent echo of futility. Can you please run our Congress? Or--what the hell anymore-- be our President! We are literally imploding over here in the good ol' US of A... I'm so happy, I guess, that I have colors to paint every dismal distressing mood I/we face in the next two years.