Jump to content

Wolf Wallis

Members
  • Posts

    56
  • Joined

  • Last visited

Contact Methods

  • Website URL
    www.broadwayextended.com

Profile Information

  • Gender
    Male
  • Location
    Maryland
  • Interests
    Writing, Music, Recording, Camping, Family, Learning

Recent Profile Visitors

1,454 profile views
  1. Just to keep you in the loop, uninstalled Photo, Designer, and Publisher 2.6. Installed 2.5.6, which worked very well for me, and all three are up and running. No issues. Sure, could be something local to my setup/configuration/etc.; however, a good app has a way of working that allows for the individuality of users. Certain buy-in requirements must be adhered to, but after that it's the company that has to produce a viable product. Look, 2.5.6 is back in my wheelhouse and earning its keep. Left the workforce and Adobe products behind when Affinity came out. Thanks for the help and encouragement.
  2. Meliora, thank you for the info. It's my MO with Mac OSs, but just didn't consider Affinity. Been my go to since I retired in 2017. Last working, acceptable version was 2.5.6 for me. I'll be going back tonight! Thanks again!
  3. Appreciate your help and explanations. I'll try a few options.
  4. Yes, thanks for mentioning that. Had to do that some years back, had forgotten. Just went through it. Only applied to AP 2 and only Reset what you see below. Did not work. I'd like to ask your recommendations as you're familiar with my particular issue and have a bit more experience. As I also brought both Designer and Publisher 2 up to 2.6, resetting all but user defaults (even that, if necessary) for all three might be advisable.
  5. Only wished to spare you the headache I'm having. Yes, duplicating an issue is tried and true and for the reason you mention. I'm glad you weren't able to duplicate any of the issues. I am still experiencing mine. Ergot, within your context this becomes a local issue as opposed to a bug experienced by others. I'll need to explore a solution.
  6. Please, don't try to duplicate the issues. You might not like it. Why doubt a reinstall of an older version would be fruitless? I was running V2 2.5.6 for quite some time and never an issue. After the 2.6 install, things are wonky. On the forums, I saw a staff member (Patrick Conner) had posted a link to previous versions and I went there and downloaded Photo V2 2.5.6. If I uninstall Photo 2.6, reinstall 2.5.6 and use my license reference, might that be a solution. 'Not much help for you' sorta points the way to drastic measures.
  7. Both Matte and Feather. Prior versions, using the matte brush worked. Border width wouldn't adjust and displayed a large border box covering most of the image when button pressed. Goes away upon button release. Another oddity, when going to the marquee selection tool, tip dialog correctly names it; however, moving the marquee selection tool over the image, it is randomly named other tools (dust and scratches, custom blur tool). Very strange. Is there a relatively easy way to roll back my version somehow?
  8. Marching ants did indeed disappear, but the Refine Selection dialog box became non-functional.
  9. Here's an odd one. A while back, I learned a neat trick allowing me to feather/vignette an item using the marquee selection tool, then going to the menu and Select>Refine Edges. Problem is, the dialog box comes up but is non-functional and the marquee selection goes away. Just yesterday, I upgraded to the new V2 2.6.0 version. Can I revert back to 2.5.3 (or the previous version) or is there a fix? OR, is this another fine example of operator error leaving me apologetic and embarrassed. Below are my particulars (haven't updated my profile in some time, sorry.). Running: Affinity V2, 2.6.0 Platform: Apple M1 Max Studio OS: Sequoia, 15.3.1
  10. Please delete this post. It is no longer necessary. This has been an exercise in operator error, big time. Have just updated Photo from the App Store to the appropriate 1.8.6. Whatever I did before didn't work. Just after posting the above concern, I went back and tried one more time...this time it worked. My apologies to staff, who work so hard to help educate others and help with meaningful issues. Also, apologize to the entire Affinity Forum. May you learn from my mistakes and exercise patience before embarrassing yourself with a premature post. Sincerely, Wolf
  11. Hello Affinity, When I first extricated myself from Adobe Photoshop, I purchased Affinity Photo from the App Store on my iMac. Photo has been working well and updating appropriately. Both Publisher and Designer were purchased directly from Affinity. Not long ago, Publisher and Designer asked if I wanted to update upon opening and both now reside at v1.8.6. I realize that my purchase from the App Store for Photo requires getting my updates from them. However, Photo will only update to 1.8.4. I've even tried downloading the app again, but only installs 1.8.4. Call me anal, but I like to follow both Apple's advice, as well as Affinity's advice. 1.8.6 across the board should be easy. Any advice? Wolf
  12. A more sophisticated function for book layout would be essential. Until then, moving pages within the thumbnails in the pages panel will have to suffice. I've laid out a 200+ page book with sections for each chapter. While I certainly found it clunky to have to go back and modify section page numbers to accommodate any manual page movement, I was able to do it. The satisfaction of being able to perform at least that operation was yet another bye-bye wink to InDesign. Petar Petrenko's comments above, as well as many other comments regarding page movement, InDesign import, and other suggestions, are spot on and the developers at Affinity need to continue burning the midnight oil. Perusing these forums show the myriad problems still inherent in Publisher. Obviously, many are user created issues and learning curve situations; however, much work still needs to be done.
  13. Apologize for the confusing post below, but this has been a confusing introduction to Publisher. Soooo happy to be using Publisher and not having to boot to an external drive running Mavericks just to get to Adobe InDesign 5.5. However, for reasons still not uncovered, Publisher has had serious and consistent crash problems since the beginning. I now see that Affinity Publisher is available on the App Store. When I purchased Publisher on original release day, it was only available through the Affinity website as a download. Going through other areas of this support forum (beta, bugs, etc.), one can find my numerous posts regarding consistent crashes. Currently, I have achieved a workaround to the crashes (generally regarded as a unique, user-oriented issue rather than the software itself). This workaround has me setting up a separate user account and using a beta build (1.7.3.475). The beta builds were suggested prior to the suggestion of setting up a separate user account. If you are confused reading this, believe me, I have been confused on my end ten-fold. No matter, at this point I am working towards updating my OS to Catalina and considering what to do about the user accounts, beta builds and basically consolidating everything back to a normal setup. In this regard, I am also wondering if I should (or could) be using the App Store version, although since I originally downloaded from the Affinity website, the App Store is listing Publisher as a purchase. How would it work to download from the App Store? I do have my Product Key and all the particulars, but don't want to be charged additional money. Just want to set Publisher up normally as I have with Affinity Photo (downloaded from the App Store) and hopefully delete this separate user account that has been preventing the crashes from happening.
  14. Walt says the build is .481, but you're right thomaso, there must be a difference, at least in reporting, between windows and mac.
×
×
  • 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.