So anyway, after finding that the sandbox workaround fixed this small issue for me, at least I have that back.Īnyways, all to say I'm disappointed that the team at Adobe doesn't seem to care about their paying subscribers. I assume it's just a glitch in the new update, but it's still very frustrating that things like this continue to happen and slip passed quality control, leaving us as paying customers to flock to a "support community" to find workarounds ourselves. I won't get into it as it's entirely unrelated, but it was the removal of a feature I use CONSTANTLY, albeit a basic one. It did however, correct another issue I began having after, you guessed it, another update from Adobe. Not sure if someone else marked that as the correct answer, and if it is for you then that's great, but this didn't do anything for the speed of the program on either my PC or Macbook. I've also tried the "fix" that cesar.cintron posted about disabling sandbox protections. It's still slow as ever just as it was from the start of this update at the beginning of the year. I've just been left in the dark, hopeful that Adobe would fix the issue in a subsequent update, but that hasn't happened. I've still spent time scouring the web for info on this with no luck. It's now been 8 months since posting this question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |