Jump to content

Search the Community

Showing results for tags 'afb-3857'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. This may not be a bug, per se, but it seems very odd to have seen the warning message (attached). AFPUB 1.8.3; Mac OS X 10.15.3 I was editing and saving a document as I went. I had also saved sequential versions as I edited (to see if any problems arose). I keyed Command + S to "save" the file, did some more edits and keyed Command + S again and got this warning message. I should not have gotten that type of message as there is no other instance of AFPUB or any other process (including Design and Photo) that would access the document in question. That is to say there could be no reason (except bugs IMHO) that the message should have popped up. I did perform a "save as" as the message suggested.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.