Jump to content

Brad Brighton

  • Content count

  • Joined

  • Last visited

About Brad Brighton

  • Rank
    Advanced Member
  • Birthday 04/30/1968

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    : Nevada, USA
  • Interests
    Stretching boundaries (literally) with extreme stitched panoramas, capturing light in all its forms, software development, team and business coaching, and a few other things that seem even more completely out of place in this list.

Recent Profile Visitors

518 profile views
  1. I'm not a Serif rep however... While the App Store purchase allows you to use the app across multiple iPads, it does not allow you to cross to macOS. You would need to purchase that version separately (either through the Mac App Store or directly from Serif depending on your personal preferences - there are other threads that discuss the differences between the two options).
  2. Also, since Serif are European, your issuing bank may be blocking the charge as possible fraud. You may need to contact your issuer on that.
  3. Brad Brighton

    File opening Order

    I have an old bug report on the topic lying around somewhere... my SWAG based on experience is that the tabs are filled in in order of _completion of load_, not _initiation of load_. Larger files in a group will wind up later in the tab order on launch/open group. Predictability among larger files is not high given variations of code performance at the time of file open, available required system resources that may vary depending on the content of the file, and speed of retrieval from underlying storage.
  4. Brad Brighton

    Ongoing lens profile issues? (Canon this time)

    Confirmed - thanks for the explanation.
  5. Hi folks, I've seen multiple threads about lens profile issues in 1.7.x but it's not clear to me if these are all separate issues with similar footprints or if they are really the same, so here's another merge-candidate thread: • 1.7.3 macOS from the Affinity Store running on Mojave 10.14.6 (MBP2018 15" Vega20) • Camera: Canon 5D Mark III, lens in question *this* time: EF24-105L IS USM Previously, I've had issues with the lens being recognized at all; this time, it appears the lens is known in the summary and the EXIF but not for profile distortion. (see screenshot, CR2 raw file for this instance attached as well) Is this another case of what everyone else is seeing or is this its own situation? Thanks! _D7A4673.CR2
  6. Getting even further off-topic, revision control is notoriously awful with binary files. Bloats the repository since there's not often a meaningful diff between one binary and another that can be applied. You wind up storing the entire file each time. Good when you genuinely need documented reproducibility at a point in time, terrible for most other workflows.
  7. That's only effective if you know where in the history the last notable save was. If you're like me and always (manually for every file, feh) have "save with history" turned on, then you're back to the close-without-saving option only.
  8. Brad Brighton

    Affinity Designer for macOS - 1.7.3

    Silly questions but the first things to check: are you (1) sure you're logged in at all at the App Store (it's been known to log people out and it not be obvious) and (2) logged in as the Apple ID under which the purchase has been made?
  9. Given the ways the App Stores intentionally separate developers and purchasers with basically the only line through that medium being reviews and developer responses, it's challenging. There is, as you found, a way to interact with Serif directly here and hopefully your feedback about the content of their responses will be taken into consideration for future messaging. I don't think I can add anything useful further to this so cheers for now!
  10. While I can understand and appreciate this, Greg, I doubt there's anything Serif could have done except explain it better. I cannot speak on the MS side but as an Apple developer, had this situation been on the Mac side, there's no one for the developer to talk to. Apple specifically tells developers they CANNOT initiate refund requests. The user/customer MUST do so. I suspect it's similar on the Microsoft side.
  11. To get this out of the way, I do NOT work for Serif nor am I an apologist. I'm going to dive in on this part only because it may be useful for any non-developers reading, either for this specific topic or generally. App Store versions (both Microsoft and Apple) of any app are NOT identical to self-distributed versions of those same apps in two critical ways: There is extra code involved to support the delivery of the app (security & receipt checking, etc) through the respective app store as well as potentially dealing with the environmental differences because of delivery method (see the next point). The "rules" of what an App Store version of an app can do by default are increasingly different than what a self-distributed app may do, predominantly centered around asset and resource access security. "What can you open?", "Where can you save?", "How do you talk to other apps?", "What hoops do you have to jump through to achieve a particular action?", etc. Neither of these is meant to be a "get out of jail free" card for Serif should there be bugs or uncaught misbehaviors due to restriction cases that weren't clear. However, the nature of software development is that the results are imperfect and the more variations there are of an environment, the more likely there will be errors that are only discovered "in the field". Serif, I'm certain, tests for as many of these as reasonable and when something breaks or is missed, works diligently to identify, isolate, and correct those issues. Add in the nature of App Store business agreements (which effectively are determined by MS and Apple, NOT Serif) and it's understandable that some audiences may feel slighted when there are issues. It's unfortunate, both that those feelings are incurred and that the remedies are fewer for Serif when working with the App Stores but that's the state of the situation in cases like these.
  12. Yeah, I'd have to agree, there are several suspicious elements here. I would recommend running First Aid on the disk but if you're going to have it looked at anyway, leave it alone and let that person see it as it is (to avoid hiding any symptoms or messages that inform the situation).
  13. :-) I wasn't focusing on the 'me' part, I was focusing on the leading slash. Are you trying to work on the file(s) simultaneously in the two apps? Your comment about only getting errors when Designer was running makes me go "huh?"
  14. It could easily be a typo in bringing the error message over so forgive the detail question -- is it "Users/me..." or "/Users/me..."? The former is highly unlikely to exist and FileNotFound errors can sometimes be lumped together with access permission errors (in that you don't have permission to access something that doesn't exist). And I do see the slash in the Desktop example, so I suspect it's "/Users/me...". Also, do I miss in the thread whether you're dealing with the MAS version or direct-from-Affinity version of AP? There could be sandboxing issues going on if you're using the MAS version. Apropos of advice you didn't ask for and FWIW, when you eventually move to a Mac that runs a newer version of the OS, you're going to have additional hoops to jump through to keep that non-Home-tree workflow unless you move it to external drives. More and more, full disk access is being restricted by default (though you CAN make exceptions, hence the hoops).
  15. Only if any development the OP may do is specifically for fonts. FTXcode and FTXViewer catch me periodically when I'm trying to install, not debug, and I *do* know what to do with fonts. These are tools that are installed but I never have a need for them. FTXcode specifically can capture that double-click; the only harm is to my vocabulary for me. For someone otherwise unfamiliar with those tools, specifically calling out the app needed may help them realize that the default open app may not be Font Book.

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.