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

Mark Ingram

(Ex) Staff
  • Posts

    5,358
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Mark Ingram got a reaction from Fion Noir in Affinity V2 on Linux   
    It's nothing to do with Apple. We haven't implemented a Linux version because there simply isn't enough support for it. I realise that's not a satisfying answer for Linux fans (which I count myself as one), but take a look at the thread linked above, 136 votes of support for Affinity on Linux. It means we would never recover our engineering costs from developing a Linux version.
  2. Thanks
    Mark Ingram got a reaction from Galan in Are legacy MSI v2 installers available?   
    Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
    Yes. These are now available
     
  3. Sad
    Mark Ingram got a reaction from Greg T in Affinity Photo v2 .exe file location   
    I've mentioned elsewhere that we use "App Execution Alias" to enable this scenario. You can find the aliases in the following location:
    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
    Please replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can launch them without even specifying the full path, e.g. AffinityPhoto2.exe.
  4. Like
    Mark Ingram got a reaction from Vorseher in Affinity Photo v2 .exe file location   
    For anyone that would like to work around issues with launching our apps from third-party applications (e.g. DxO, ACDSee, etc), I have written a launcher utility that you can place anywhere on your system, and it will take care of calling our apps, with any required arguments.
    Usage: aflaunch -a name -b build [args] -a name : One of the following Designer2 Photo2 [Default] Publisher2 -b build : One of the following Retail [Default] Beta MSStore args : [Optional] All remaining arguments to be passed onto the target application (must be last)  
    The -a and -b arguments are optional, so you can ignore them unless you want to launch a different app, or the beta or MS Store versions.
    I have signed the exe as well, so it will have a valid digital signature.
    Please let me know how you get on with this.
    Updated: 12/11/2022 @ 11:04am UTC. Now deals with spaces in filenames.
     aflaunch.zip
  5. Like
    Mark Ingram got a reaction from SVVector in Are legacy MSI v2 installers available?   
    Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
    Yes. These are now available
     
  6. Like
    Mark Ingram got a reaction from Fist of the mighty Bob in Are legacy MSI v2 installers available?   
    Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
    Yes. These are now available
     
  7. Like
    Mark Ingram got a reaction from Thomahawk in Export to WMF/EMF   
    That won't happen because those formats rely on Windows APIs to write them.
    In this day and age, there really is no need to use WMF or EMF, there are many better formats to choose from.
  8. Thanks
    Mark Ingram got a reaction from charactersword in Are legacy MSI v2 installers available?   
    Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
    Yes. These are now available
     
  9. Sad
    Mark Ingram got a reaction from camelia in Are legacy MSI v2 installers available?   
    Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
    Yes. These are now available
     
  10. Like
    Mark Ingram got a reaction from AprilSpring in Why are we using MSIX for Windows installers?   
    Pros:
    MSI had an installation success rate of ~85% (and we have many requests to our tech support team for v1 install failures). MSIX promises a 99.9% success rate.  MSI requires admin privileges to install. MSIX installs per-user, but files are deduplicated so that disk space isn't wasted. MSI apps are not sandboxed from other applications, meaning other applications can break those apps (we have seen this with several third-party apps in the past). MSIX apps are sandboxed to prevent this. MSI updates require a manual download of the full ~550mb installer which must be manually installed. MSIX can perform in-app delta updates which are smaller and faster. MSI updates can only be performed one at a time. MSIX can update all three apps simultaneously. MSI cannot guarantee that an uninstall will leave your machine in the exact state prior to install. MSIX installs are segregated and don't rely on the registry or special filesystem locations meaning an uninstall always leaves you in a clean state. Installation and app data paths are cleaned on uninstall. MSI apps cannot integrate with Microsoft Photos app to provide "Edit In..." style features. MSIX can. MSI does not require a digital signature. MSIX does (this means any MSIX that appears to be from Serif, will be guaranteed to be from us and only us). Cons:
    MSI can allow the user to change the installation directory. MSIX can move installed apps to different drives, but it cannot choose a specific directory (due to the sandbox). See below: MSI can allow an option to install a desktop shortcut. MSIX doesn't provide this as an option, but you can pin the apps to either the Start Menu or the Taskbar. There is also the secret Shell:AppsFolder location in Explorer that allows you to right-click or drag the icon to your Desktop for a shortcut as a workaround if you need it.  MSI has easy discovery of undocumented app locations for launching from a third-party. MSIX hides the install location due to the sandbox, but we use App Execution Alias to enable this scenario. You can find the aliases in the following location: C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
    Remembering to replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can often launch them without even specifying the full path, e.g. just AffinityPhoto2.exe. There are bugs in some third-party applications with the App Execution Alias , and the next post includes aflaunch.exe as a work around if you need that instead. 
     
  11. Like
    Mark Ingram got a reaction from mrqasq in Are legacy MSI v2 installers available?   
    Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
    Yes. These are now available
     
  12. Like
    Mark Ingram got a reaction from delta-sierra in Affinity V2 on Linux   
  13. Thanks
    Mark Ingram got a reaction from Harry_ in Affinity products for Linux   
    It's not up to us to get it working on Linux - as far as we're concerned, it's an unsupported platform, regardless of whether that's native, or via WINE or anything else. 
    With regards to the canvas flickering, it uses Direct3D11 to present the document to the screen (separate to the UI rendering in hardware, which is done by WPF/Microsoft). You may have more luck by changing the renderer to WARP in the Preferences, if that is detected (WARP is a software rasteriser for Direct3D).
  14. Like
    Mark Ingram got a reaction from Display in Are legacy MSI v2 installers available?   
    Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
    Yes. These are now available
     
  15. Sad
    Mark Ingram got a reaction from Display in Why are we using MSIX for Windows installers?   
    Pros:
    MSI had an installation success rate of ~85% (and we have many requests to our tech support team for v1 install failures). MSIX promises a 99.9% success rate.  MSI requires admin privileges to install. MSIX installs per-user, but files are deduplicated so that disk space isn't wasted. MSI apps are not sandboxed from other applications, meaning other applications can break those apps (we have seen this with several third-party apps in the past). MSIX apps are sandboxed to prevent this. MSI updates require a manual download of the full ~550mb installer which must be manually installed. MSIX can perform in-app delta updates which are smaller and faster. MSI updates can only be performed one at a time. MSIX can update all three apps simultaneously. MSI cannot guarantee that an uninstall will leave your machine in the exact state prior to install. MSIX installs are segregated and don't rely on the registry or special filesystem locations meaning an uninstall always leaves you in a clean state. Installation and app data paths are cleaned on uninstall. MSI apps cannot integrate with Microsoft Photos app to provide "Edit In..." style features. MSIX can. MSI does not require a digital signature. MSIX does (this means any MSIX that appears to be from Serif, will be guaranteed to be from us and only us). Cons:
    MSI can allow the user to change the installation directory. MSIX can move installed apps to different drives, but it cannot choose a specific directory (due to the sandbox). See below: MSI can allow an option to install a desktop shortcut. MSIX doesn't provide this as an option, but you can pin the apps to either the Start Menu or the Taskbar. There is also the secret Shell:AppsFolder location in Explorer that allows you to right-click or drag the icon to your Desktop for a shortcut as a workaround if you need it.  MSI has easy discovery of undocumented app locations for launching from a third-party. MSIX hides the install location due to the sandbox, but we use App Execution Alias to enable this scenario. You can find the aliases in the following location: C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
    Remembering to replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can often launch them without even specifying the full path, e.g. just AffinityPhoto2.exe. There are bugs in some third-party applications with the App Execution Alias , and the next post includes aflaunch.exe as a work around if you need that instead. 
     
  16. Thanks
    Mark Ingram got a reaction from SrPx in Justification by faith in Microsoft. Really? The MSI/MSIX kerfuffle   
    I've been involved in discussions with Microsoft since the inception of this, and I can tell you that their intentions are to increase the stability of Windows and improve the experience of end users. There is no maligned conspiracy to "take away control". They want a nice isolated experience for application developers so that they can guarantee their applications won't be affected by other third parties (which we have seen in v1).  That does simplify things, which some users may not be happy with, but generally people just want their applications and their machine to just work. 
    Tim Sweeney is great, but he is also in the business of running an App Store, so he's hardly unbiased here.
    I fully support the idea that third parties don't share customer data with us. Privacy is important. We allow customers to purchase from Apple or Microsoft because those users trust them with the personal details and their credit card details. You may not like those companies, but that doesn't mean that all of our customers feel the same way.
    ----
    And with that final point, I would like to say, these forums are not representative of our overall customer base. The forums are a location that people come to when they have problems, or when they want to be actively involved in feature discussions or partake in the beta tests. They are not the place where our average user goes to say "Everything was fine, thanks.". I feel like a lot of discussions here are skewed by the belief that some percentage of users on the forum represent the overall feeling of our customers. 
  17. Thanks
    Mark Ingram got a reaction from Kenneth Weidlich in Why are we using MSIX for Windows installers?   
    Pros:
    MSI had an installation success rate of ~85% (and we have many requests to our tech support team for v1 install failures). MSIX promises a 99.9% success rate.  MSI requires admin privileges to install. MSIX installs per-user, but files are deduplicated so that disk space isn't wasted. MSI apps are not sandboxed from other applications, meaning other applications can break those apps (we have seen this with several third-party apps in the past). MSIX apps are sandboxed to prevent this. MSI updates require a manual download of the full ~550mb installer which must be manually installed. MSIX can perform in-app delta updates which are smaller and faster. MSI updates can only be performed one at a time. MSIX can update all three apps simultaneously. MSI cannot guarantee that an uninstall will leave your machine in the exact state prior to install. MSIX installs are segregated and don't rely on the registry or special filesystem locations meaning an uninstall always leaves you in a clean state. Installation and app data paths are cleaned on uninstall. MSI apps cannot integrate with Microsoft Photos app to provide "Edit In..." style features. MSIX can. MSI does not require a digital signature. MSIX does (this means any MSIX that appears to be from Serif, will be guaranteed to be from us and only us). Cons:
    MSI can allow the user to change the installation directory. MSIX can move installed apps to different drives, but it cannot choose a specific directory (due to the sandbox). See below: MSI can allow an option to install a desktop shortcut. MSIX doesn't provide this as an option, but you can pin the apps to either the Start Menu or the Taskbar. There is also the secret Shell:AppsFolder location in Explorer that allows you to right-click or drag the icon to your Desktop for a shortcut as a workaround if you need it.  MSI has easy discovery of undocumented app locations for launching from a third-party. MSIX hides the install location due to the sandbox, but we use App Execution Alias to enable this scenario. You can find the aliases in the following location: C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
    Remembering to replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can often launch them without even specifying the full path, e.g. just AffinityPhoto2.exe. There are bugs in some third-party applications with the App Execution Alias , and the next post includes aflaunch.exe as a work around if you need that instead. 
     
  18. Like
    Mark Ingram got a reaction from Snapseed in Are legacy MSI v2 installers available?   
    Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
    Yes. These are now available
     
  19. Thanks
    Mark Ingram got a reaction from DigitalTux in Extremely disappointed that this installs as an "App" and not regular software program   
    Hi all. Thanks for your patience over the weekend when our offices were closed.
    We've had a meeting this morning and decided to ALSO offer MSI installers to those people who would like them. I can't tell you when this will happen, as there is engineering work that will be required to allow this to happen, but we hope it won't be long.
    Thanks for your feedback!
  20. Thanks
    Mark Ingram got a reaction from hifred in No .exe, no interest   
    Hi all. Thanks for your patience over the weekend when our offices were closed.
    We've had a meeting this morning and decided to ALSO offer MSI installers, to those people who would like them. I can't tell you when this will happen, as there is engineering work that will be required to allow this to happen, but we hope it won't be long.
    Thanks for your feedback!
  21. Like
    Mark Ingram got a reaction from laurentia in No .exe, no interest   
    Yes - if you already have the MSIX installed, it'll prompt you to update and perform the update in-app. There's no need for you to change anything 🙂
  22. Sad
    Mark Ingram got a reaction from Muldune in Why are we using MSIX for Windows installers?   
    Pros:
    MSI had an installation success rate of ~85% (and we have many requests to our tech support team for v1 install failures). MSIX promises a 99.9% success rate.  MSI requires admin privileges to install. MSIX installs per-user, but files are deduplicated so that disk space isn't wasted. MSI apps are not sandboxed from other applications, meaning other applications can break those apps (we have seen this with several third-party apps in the past). MSIX apps are sandboxed to prevent this. MSI updates require a manual download of the full ~550mb installer which must be manually installed. MSIX can perform in-app delta updates which are smaller and faster. MSI updates can only be performed one at a time. MSIX can update all three apps simultaneously. MSI cannot guarantee that an uninstall will leave your machine in the exact state prior to install. MSIX installs are segregated and don't rely on the registry or special filesystem locations meaning an uninstall always leaves you in a clean state. Installation and app data paths are cleaned on uninstall. MSI apps cannot integrate with Microsoft Photos app to provide "Edit In..." style features. MSIX can. MSI does not require a digital signature. MSIX does (this means any MSIX that appears to be from Serif, will be guaranteed to be from us and only us). Cons:
    MSI can allow the user to change the installation directory. MSIX can move installed apps to different drives, but it cannot choose a specific directory (due to the sandbox). See below: MSI can allow an option to install a desktop shortcut. MSIX doesn't provide this as an option, but you can pin the apps to either the Start Menu or the Taskbar. There is also the secret Shell:AppsFolder location in Explorer that allows you to right-click or drag the icon to your Desktop for a shortcut as a workaround if you need it.  MSI has easy discovery of undocumented app locations for launching from a third-party. MSIX hides the install location due to the sandbox, but we use App Execution Alias to enable this scenario. You can find the aliases in the following location: C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
    C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
    Remembering to replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can often launch them without even specifying the full path, e.g. just AffinityPhoto2.exe. There are bugs in some third-party applications with the App Execution Alias , and the next post includes aflaunch.exe as a work around if you need that instead. 
     
  23. Thanks
    Mark Ingram got a reaction from JET_Affinity in No .exe, no interest   
    Hi all. Thanks for your patience over the weekend when our offices were closed.
    We've had a meeting this morning and decided to ALSO offer MSI installers, to those people who would like them. I can't tell you when this will happen, as there is engineering work that will be required to allow this to happen, but we hope it won't be long.
    Thanks for your feedback!
  24. Thanks
    Mark Ingram got a reaction from DCY2 in Are legacy MSI v2 installers available?   
    Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
    Yes. These are now available
     
  25. Like
    Mark Ingram got a reaction from P3Ci in Are legacy MSI v2 installers available?   
    Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
    Yes. These are now available
     
×
×
  • 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.