Jump to content
You must now use your email address to sign in [click for more info] ×

Egged

Members
  • Posts

    19
  • Joined

  • Last visited

  1. Have been in contact with Extensis, developer of Suitcase. I'm running Suitcase 8, and they suggest subscribing to the new Suitcase, which is supposed to play well with Affinity programs. For as often as I use font management, I really don't want to subscribe (it's why I switched to Affinity from Adobe), but do have to wrangle thousands of the pesky little critters. I want a way to preview fonts easily as well as turn them on and off. Does anyone have a recommendation for a font manager known to play well with Affinity? It doesn't have to be free, but I would prefer to buy (not subscribe). Thanks for all the support!
  2. Got the box back from the Mac Croaker. I have Suitcase Fusion 19.1.1 as a font manager and it is fouling APhoto. Even if Suitcase isn't running , it is causing problems. Opening Suitcase Preferences and clicking “Stop Suitcase Fusion Type Core” allows APhoto to run properly. Suitcase starts when the box is started, so Prefs have to be opened and Type Core turned off to run APhoto (hope I remember that). Why it is doing this now is a puzzle, since I've been using it for years. I notice Suitcase's "Update automatically" was also "on" and it may have updated without my noticing. Shutting down Suitcase also seems to have solved the Arial font corruption, but why that was happening is still a mystery. Just happy it's working.
  3. Did that last week, and removed the problematic ones. What's funny is that page looks fine on a restart, and only looks like this after 5 or 10 minutes. Going back to the Apple Quack today, and won't sign on again for a spell. Thanks all for your help!
  4. That was harder than I thought it would be! Had to use the iPad camera to take a shot of the prefs, which is why it looks fuzzy. As for the Arial font corruption, attached is a pic of the Kindle page, which looked normal on starting the computer, and looks like the picture after 5 or 10 minutes.
  5. I reloaded the software from the Apple Store, so it's running at default settings. But I tried it anyway, and APhoto runs about 5 or 10 minutes with each operation becoming slower than the last until it finally stops responding altogether. I'm not talking complex commands, just simple things like using the eraser tool or dodge/burn tool. I believe it is a hardware problem, though. The font Arial works fine on starting, but will become corrupt after the same amount of time.
  6. Brought home the computer from the Apple Quack with new memory and it runs faster. The diagnostic on the hard drive showed it was running slower, but had no issues. APhoto opens and runs normally for about 15 minutes, then begins slowing down. APhoto then stops, and won't respond to any cursor or keyboard commands. I trashed APhoto and downloaded it again from MAS. It didn't work. I turned off the computer for the weekend and opened it again yesterday. Ran 15 minutes and acted as above. Ditto today. So I believe I need to decide on whether to buy a new computer or repair this one. Designer and Publisher still work normally.
  7. I copied the error message just as it was displayed. As for "HUH?", that's exactly what I said! I was working in a Designer doc, and wanted to add an element produced in Photo when the problem occurred. I habitually have two or three Affinity programs open and running at one time. But APhoto doesn't work at all now, even if it's the only program running. Think I better take my computer to the Apple Quack. At 9 years old, it may be suffering from age related problems of which APhoto is the first symptom.
  8. Thanks for the advice! I will do things differently when I get a new computer. This one was my old work computer and was originally configured offsite. I just moved my working files over from a back-up drive to the hard drive and suffered no permissions issues or problems for 8 years. APhoto was purchased from the app store and updated through them. It has worked well for a year and a half. APub and Designer were purchased from Affinity, and they still work fine. As for the error messages, they just started the day of the my post here. I eliminated my name and inserted "/me/" when writing out the error message. Yesterday, I was able to restart and APhoto worked normally, only to stop and give error messages when Designer was running. Today APhoto doesn't work at all.
  9. I know it sounds strange, but I've never used my home folder to store anything, since I'm the only user. I've always just created a folder on the hard drive for specific subjects and saved in them, since I've done it that way for decades now. I have separate folders for many different active projects and folders with finished projects. Update: I tried creating a new APhoto document today, and it won't allow it to be saved even to the desktop. Trying to save as an afphoto generated a message saying: "Failed to save document: /Users/me/Desktop/name.afphoto" and "Save failed because you do not have permission to create a file in that location." and bleow that "Do you wish to save the document to a new file?" So I tried exporting as a jpg and got: "An error occurred while exporting to: Users/me/Desktop/Name.jpg" and "The file could not be created." Designer and Publisher work as expected.
  10. I used the example in the screenshot because it was in APhoto's "Recently Opened" menu, since I had just been working on it for Halloween. All the photo folders (i maintain several by subject) are on my hard drive rather than in my home folder. Currently APhoto won't open anything, but APub ad Designer work as expected. I'm wondering if I should try and reload the software, since this began after having to force quit APhoto. Thanks for the reply!
  11. Yesterday, I had to force quit APub, APhoto and ADesigner, then restart iMac mid-2011 desktop (OS SIERRA 10.12.6). Then Designer ran normally, but upon completing a project and saving it as a jpg, APhoto told me I didn't have permission (screenshot of the error attached). After a restart, Photo opened jpgs, but upon opening Designer again, Photo gave the same error message. Starting the computer this morning, Photo (as the only program open) won't open anything and just gives the error message "Failed to open file; The file could not be opened because permission was denied." I had just recently downloaded Firefox 70.0.1. That is the only recent change, and I mention it because Publisher runs slower if Firefox is running
  12. I learn something new everyday. I didn't realize I had created the box that way. I'd better slow down. Thanks!
  13. Hmm, So that's it! I must've done the same thing. Don't know HOW I did it, but it's repeatable. Thanks!
  14. I just installed A Pub 1.7.0.139 and began work on a large document almost finished. I added new pages, added photographs, and linked text to a new page. The text on the page it was linked from was fine, but the text on the next page was flopped and read backwards. I scrubbed the text of formatting, no luck. I reflowed the text completely, no luck. I finally deleted the offending page, created a new one and the problem was solved. Next, I tried to move a caption nearer its picture only to have the text flop backwards. I went through the same rigamarole and wound up deleting the pic and caption box and redrawing and reinserting both pic and text to solve the prob. I'm not the sharpest knife on the team, more like a dull axe, so forgive me if I made rookie mistakes, but this one has me flummoxed.
  15. Well, that's worse than what's happening to me. In my case, after closing the document and trying to reopen it, I get the "open recovered file" option, then when I click on it, I get the "file open in another application" alert. I can't open the file until I quit and relaunch APub, but I haven't had to restart the computer to do so.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.