shushustorm

There isn't any scripting support in V2 yet. We have a dedicated scripting team here typing very quickly but still no definite timeline for release yet. 

Affinity will support Javascript and also have a 'C' based API binding interface that people can use to write plugins. We will also have the ability to create UI to support their scripts and plugins with dialogs and panels. 
We have a team developing this but the amount of work is very large so unfortunately users will need to be patient.

Further information regarding scripting can be found in the following Affinity dev responses - 
I hope this clears things up

They did: ADe & APh 1.8.4 from the Mac App Store still run on Mountain Lion. I still have them installed on a that partition.
v1.9 and above required at least Mavericks, I guess. So in 2019 I finally moved over to El Capitan…

It's less problematic as most users could just update to the next version. Generally speaking, it was better to update than not for the QoL improvements. With V2, the user who files available online for distribution has to specify the version. This can create headaches especially if people don't read closely enough (common). It makes the format a deadend (imo) for asset designers unless they were to take the trouble to export both and include them. That isn't helpful though for designers who only pick up v2.

Agreed. Although, this doesn't specify whether the feature is intended to be added or not. The question here should be, is this high enough on the priority list Serif intends their format to be an open one or will it remain locked for each version?

The issue with this workaround being the final solution is that for copy & paste to work, both versions would have already been installed on the machine. This defeats the point in many scenarios.
Ideally, if someone creates a template anywhere for distribution online in a shop or asset marketplace, for example, this means they now have to provides files to output for both versions. There's also no way to tell by file extension which version the software supports without the person who saved the file specifying.

Backwards compatibility is not about making V1 do V2 things. It's about V1 compatible data being ported from V2 to V1. Of course, that would strip V2 features that are manifested in the file format, which still leaves you with maybe 99% of features being compatible.
For reference:
Dedicated topic:
Current Serif stance:
 

This is a suggestion, I feel more confortable buying a software that I know I can "own" and no servers are needed to activate.
I own a legal copy of Adobe CS3 Web Premium, have the box and everything and after I couldnt install it recently contacted Adobe. They shut down the servers, so people with a legal copy cant activate the software... (needed a software which they no longer sell even in subscription)
Or maybe a promise that we get offline activation at the end of the V2 lifecycle?

What he said is that the universal license requires you to connect to the internet to activate it. In case someone can't, like corporations doing it for security reasons, then they can't activate it. If outage or a disaster happens to Affinity servers, or if they decided to shut them down, you won't be able to install it on new hardware. This means you lost your right to use it.

Hey everyone!
Still not possible using V2.
Since suggestions for V1 are now considered "Archive", I am posting this one here again.
Here is the original topic:
 

Once you have a file in Live Docs I think it will open there, instead.

Hey everyone!
Congratulations on the release of V2!
- Quite pleased to see V2.
- Quite pleased to see no subscription.
- Not so pleased to see no High Sierra support (but understandable to some point).
- Not so pleased to see no V1 file compatibility (not understandable).
Please include a simple 1.X importer and exporter. You already have that for 1.X. You should (?) be able to integrate it with V2 in a quite straight forward way, unless you went crazy on the most basic systems you have.
I know I can import and export to .psd, but that will leave behind everything that's Affinity. I'd like to only leave everything behind that's Affinity V2 in the process when transferring between V2 and V1.
On some hardware, I still require High Sierra for some stuff. I could update my iPad versions (and get Publisher that doesn't exist as version 1), but without being able to port the files between V1 and V2, that's going to be a headache.
Please be aware that by not including this, you're going to split up your user base. To which degree, of course, I don't know. But it will happen. Some people
- will still require to or want to work with older OSs you don't support,
- won't be able to or won't want to invest the money to upgrade the entire suite, especially with the prices increased and the 40% off period being over,
- won't want to even upgrade one software when this means breaking links between, for example, V2 Photo and V1 Designer as well as V2 Photo and V1 Publisher,
- are completely satisfied with V1 already and don't see a point in updating to V2,
- don't like or have trouble using the new UI,
- just decide updating isn't worth it (yet), because the new features aren't (yet) worth the cost for updating,
- face bugs in V2 that weren't there in V1.
User base fragmentation means
- fewer bug reports, resulting in less reliable software,
- a number of people having issues with your software, because they need to exchange files with someone from the other group (V1 VS V2) making your software, at best, bothersome to use or, depending on the situation, completely unusable or just not efficient enough to accomplish the required results,
- people being frustrated, because of going V2 with a trial or buying one of the softwares, saving a bunch of files, and not being able to go back (that's huge!),
- some users will trust your software less, since a new version created such a messy situation.
I think a simple Exporter and Importer for V1 files could very well be worth the effort.
Now personally, I am going to buy the entire V2 suite anyway, because V1 did serve me quite well (started using Designer before 1.0, it's almost been a decade now) and for a reasonable price as well and I will probably have to update eventually, in a few years. But still. Would be great to go back and forth between V2 on iPad and V1 on desktop.
I searched for "v1" and the search stated there were 0 results.
Best wishes,
Shu

And Vectornator

In the old version, the spacing and icons were much larger, so it was easier to use

I infact solved with copy/paste.
Hopefully I've saved only a file...
I'll update V2 probably but this "forces" to update to the whole package. And you have to be sure any other colleauge you share files with have same version....not the best thing.

I installed the Affinity V2 Designer/photo to test it.
No substantial differencies for my use....or not at all.
Only a bug in photo that was never corrected and now is (lazo selector mantaining last setting).
Problem is...I've saved a file with V2 and in V1 is no more usable!!!
I think retro-compatibility is necessary, mainly with projects shared with other people.

I am most disappointed with the fact that Affinity's second suite is not compatible with the earlier version, despite some minor differences. For example, by editing an old .afphoto project in Photo 2 by simply hiding the layer (without using the new features), we will prevent this file from being opened in the old version. Moreover - as it happened in my case - more complicated layers (Compound) could not be displayed properly in the new version.
When the developers mentioned something about version 2 a few years ago, I expected that after its premiere we would actually get a new product with a lot of additional tools that were demanded by users on the forum, but in the meantime we get practically the same product, with the number "2" added, changed icons (the UI is basically the same, with little and unnecessary changes) and with a lot of bugs.
The 40% promotion for the entire Suite (which includes both OS licenses) is tempting, but I got used to the current version, which at least is stable and runs smoother.

And what Publishing tool does Adobe offer on iPad exactly?

With all due respect, but your position and arguments are ridiculous. Every software upgrade offered by a commercial company comes with a price. You can now purchase the app(s) at a 40% discount and that's quite generous.

This is an outlier in the software world.  If my memory serves me correctly there was one charge once for an upgrade, but that may have been from 7 to X. Final Cut and Motion are two pieces of software I have used for years and years with no upgrade charge. Consider though how much Apple makes from its phones, they are awash in cash.

An "unlink global colour" button in the colour panel would also make it much easier to change the colour of an object which currently has a global colour assigned to it.
At present, for an object with has a global colour assigned, the default colour panel shows options for tint & opacity/noise, with a button to "edit global colour". If you wish to "detach" the global colour for this particular object, you have to select a different colour panel interface from the drop-down, either the wheel, sliders or box. (Note, you can also double-click the fill/stroke colour switcher to achieve the same result).  Ideally, an "unlink global colour" button next to the "edit global colour" would then *automatically* switch the colour panel back to the wheel, sliders or box interface, which I believe would make for a faster and more intuitive UI. thanks

Interesting...  admittedly I had not tried this in a few versions, and no, I was doing it correctly, but this did not work previously.  They must have fixed this in one of the more recent versions and I either missed it in the release notes or it was done quietly and not specifically noted.
Either way, I am glad that they did at least get it working for gradients.
As you pointed out, it is also working for some of the FX, such as the outer glow color, when applied from the Layers panel, but not from the Effects panel (which I never use except when testing something pointed out by someone else).  That did not work before either (from the Layers panel), so evidently something did get fixed at some point for these as well.

That indeed looks like a bug. As seen in the screenshot below, when you apply an effect using the Effects palette, the color picker doesn't seem to recognize global colors. The swatches don't have that small "global color" triangle in the corner.

The solution is to apply the effects using the Layers palette. You'll see that the global colors are treated as such (notice the small triangles in the bottom left corner).

They work fine here. You are doing something wrong.

2022-10-13 12-13-53.2022-10-13 12_17_28.mp4  

It is not just FX.
Global colors don't work correctly with gradients either, for example.
You can select a global color to be used on a gradient stop, but it basically copies the color as it exists at that time and does not remember the global color assignment, so if you later change the global color, the gradient/FX/etc. does not pick up the change.