All understood Steve. As I said, I don't expect people to load CS6 just to work out how to troubleshoot it. But it is frustrating to know that there are people on this forum who obviously have a fairly significant knowledge of the software, but answer every CS6-related question with 'it's not supported', 'it won't work on retina Macs', 'you need to upgrade to CC', 'you need to downgrade your OS' or something similar. Why not 'people have got CS6 running successfully on modern Macs' and suggest a search of this forum. There are a lot of very useful answers from people on this forum. I'm trying to add to them where I can, but having to repeatedly refute the 'won't work' answers is something that shouldn't really be necessary. There are countless people who cannot afford the significant long term cost of upgrading to CC and countless others who don't want to lose access to their files by upgrading to CC (which WILL happen if they ever stop paying). Both these arguments against upgrading have long since been hashed out, but they are still real issues that will keep people on CS6 for some time to come. ... View more

You can't seriously say 'most people' with any sort of conviction Steve. You only see people who come here with problems. All the people who have it running successfully generally wouldn't visit to tell you that they have no problems. We have no idea how many people are running it without any issues. Using your criteria you could say with equal conviction that 'most people have problems when they install and try to use Indesign CC2017', judging by the number of reports you see on this forum. That is presumably not the case. If people have problems with CS6 they can come here and ask, just like the people who come here to seek help with CC2017 problems. There should be no difference. And nobody should realistically expect Adobe to give them any support on a personal level. If that was an option forums like this would have very little reason to exist, and yes I have had significant amounts of time wasted trying to get Adobe support in the past. If Adobe were interested in listening to and supporting their customers they would have kept a perpetual licence. This bit is just my opinion... and that of tens of thousands of other Adobe customers... ... View more

Thanks Derek, I agree that this is generally a friendly and useful forum. But you're very wrong if you think I'm giving my opinion. I'm giving facts based on real world experience. I never claim that these answers are absolute because as Uwe says, there are any number of other factors than can tip things over - with any version of Indesign. Something that works for me personally on a given set-up may not work for all others, but it does allow me to state as fact that it is possible and can work, and so this information might be used and useful to others. But, there are a few forum regulars who give opinions based on their views, which are not supported by facts, and they do bury the useful answers by the very frequency with which they post their opinions as answers. A case in point was where an answer was posted that addressed the OPs problem and fixed it for them, and for a number of other people. The 'marked correct' answer was given as your problem is running CS6 'downgrade your OS or upgrade to CC'. When it was pointed out that the actual answer had been given further down the thread and suggested that it should be marked as correct, the regulars jumped in and rubbished the suggestion with their opinions. How is that useful? ... View more

Hi Uwe I agree with most of what you say. The issue that occurs fairly frequently on this forum is people who are respected for their broad knowledge on Indesign saying flat out that it is not possible to run CS6 on current MacOS or that it doesn't work with retina screens. I'm guessing that those same people have never even tried running CS6 on modern systems. I don't expect them to as they, like a lot of others have fallen into the CC system and don't have any need to use CS6 any more. But, if they have no knowledge of the realities of using it then they should refrain from making absolute statements on a subject they don't understand. As you say, any version of Indesign can be made unstable by OS updates or people using third party extensions to other software, so there is no greater risk to use CS6 than there is to use CC2017. You say yourself that problems 'could' occur using CS6, not 'will' occur. And while it is obvious that CS6 will not be getting bug fixes from Adobe, from my long history of working with Adobe products - and Indesign since version 1.5 in particular - I can categorically tell you that a lot of bugs are never fixed. I can also say that CS6 will never have any new bugs introduced but CC2017 will definitely gain new bugs with every update. CC2015 ended it's life with a fair few irritating bugs still unfixed. I suggest that they will also never be fixed because Adobe have now moved on to CC2017. On a personal note, I run Indesign CS6 (the full versions, not the CC version) every day and all functions work as well as they ever did. It is extremely fast on a brand new iMac using Sierra. I also use CC2015 every day and experience some crashes, palettes that disappear, workspaces that can't be applied, and things like the layers palette losing its little boxes so that I can't move things between layers. trashing and restoring preferences of course fixes these, most times, but they all return after a fairly short time. Restoring preferences often causes the CC syncing preferences to disappear so that every time you make a new colour for example it gets synced to the Creative Cloud because there is no way to tell it not to. CS6 NEVER crashes or exhibits irritating behaviour anything like this. I don't use CC2017 as in testing we have done it is too slow but also because of the huge number of reports of it's instability. We revisit it occasionally when we have time, but it's still not worth rolling it out to our studio Macs until it settles down. ... View more

Thanks Steve, I do try to help CS6 users when I have time, but most times any practical advice I offer is drowned out by the 'it's not possible' brigade of forum regulars. Then again those same forum regulars are kept very busy by the incessant floods of people who are having problems with CC, so it's surprising that they are able to spare the time to shoot down practical advice from others. But then I guess they don't waste any time checking their facts so it doesn't take them much time... ... View more

Sara, if you do sort out your licence then there is a good chance CS6 will actually run on your brand new Mac. Unfortunately there are a few people on these forums who endlessly repeat their 'CS6 will not work because it is not supported' mantra and 'it's a huge risk using CS6'. It is just their opinion and has no basis in fact - reinforced by the fact that they can never qualify why it won't work or why it is a huge risk. Running the latest CC2017 is just as much a risk - or more of a risk if you read these forums and see the amount of people having problems with it. I use both versions every day and CC gives me far more problems. The beauty of CS6 is that what you see is what you get and it just runs, whereas CC2017 is constantly having new bugs added. Those of us who have stuck with CS6 and have it running beautifully on the latest Macs under the latest MacOS (Sierra) are referred to by them as 'lucky' - perhaps because we have software with very few bugs that runs very fast. CS6 runs now just like it always has. ... View more

Best to try and troubleshoot your problem with the folks at FAP rather than potentially jumping out of the frying pan into the fire by switching to another product. I found the FAP support guys to be excellent and very quick and willing to help troubleshoot. In my experience FAP has always been fast running, clean and simple to use, Suitcase for me has always been a slow buggy, crashy product... and still is in it's most current version. We use Suitcase every day at work and it is always a relief to go to my evening job and use FAP ... View more

Thanks for persisting with trying to help me Karl. I've tried using 'save as', but still with no improvement, so I have shared the file with you. ... View more

I created a 'dropdown list' field and named it 'LayerConfig'. ... View more

No, I am not getting any errors in the Javascript debugger console. I have pasted your script directly into a document level javascript (from the link you gave me earlier). This script included restoreLayerConfig(this) as the last line of the script? ... View more

I have put the one line saveLayerConfig(this); into a 'Document Actions' 'Document Will Save' script. The main LayerConfig script is set as a 'Document Javascript'. This is new territory for me so I could well be getting this completely wrong still. ... View more

Thanks for all your help guys, but I think I've bitten off more than I can chew here. I don't really have enough knowledge of javascript to understand how Karl's code works, or to troubleshoot it with my PDF. I've tried using the script you pointed me to Karl and while it seems to gather the layer states information in the drop down field, it doesn't keep the layer states on reopening. I may have to try a cruder method, without layers, and just rely on using show/hide for all the content. It's quite messy and labour-intensive, but I should be able to get it to work within my abilities. I do appreciate you trying to help me. Thanks ... View more

Much appreciated. Thanks for your help Karl. ... View more

Thanks Karl I suspected that would be the case, but I'm not sure where to look for an example of how to script this. Are you able to point me to any examples? ... View more

Correct Migintosh - complex effects like gradients and raster effects won't make the transition well, or at all. Sometimes you may also have issues with complex paths and if the Illustrator file is too complex Indesign will convert it to an EPS on paste which you can't edit in Indesign. ... View more

You can also copy and paste from Illustrator to Indesign, then continue to edit the vector in InDesign. In most instances you would use the workflow Barb provided, but sometimes it's easier to work solely in InDesign. Personally I find InDesign's tools are far better for drawing and editing vector than the equivalent tools in Illustrator. ... View more

blancaa - yes, this works in a regular interactive PDF. It's using built in functions so it should be pretty bulletproof. I would suggest the simplest way would be setting up two text fields and one button. One text field is for the user to enter their answer. The other text field can be the 'correct answer' field and have the correct answer pasted into it as its default content (do this in Acrobat). Make that field read only and hidden and then use the button to show it. You could also use the button to 'show/hide' layers and have the answers on an individual layer that is only revealed when the button is clicked. You'd set up each answer on a separate layer in your Indesign file, check the export PDF layers option when making the PDF, and then set up the button functionality in Acrobat. It's a little more cumbersome to work with, but gives a nicer looking result. There are many ways to approach this, including relatively simple javascripting, so just go with whichever way works for you. ... View more

Steve's correct, this could be fairly simply done with a bit of Javascript. Make the 'correct answer' a hidden field and then decide what condition should trigger it to be a visible field. But even simpler could be if you used hidden fields and buttons to reveal them. The users could type their answers then click the button to reveal the correct answer/hidden field. There is a built in 'show/hide fields' button action in Acrobat that could be used to achieve this without any scripting needed. It all depends on whether you trust your users to not click on the correct answer before entering their own! ... View more

On a Mac you don't need to quickly hold down the keys after relaunching. Hold down the keys first then click on the InDesign icon in the dock and select 'Open' - much more relaxing ... View more

Indesign CS6 runs perfectly well on Retina iMacs. It seems to just be the laptops that have this blurry issue. Indesign CS6 also runs brilliantly with MacOS Sierra - it's extremely fast and the minor glitches we used to see occasionally with El Capitan seem to have gone away. So while it may have reached end-of-life for Adobe's purposes there's still plenty of life left in it, and there's STILL no compelling reason to move to CC. ... View more

Thanks Blublok. I'll persevere with it and see if I can get it working. ... View more