VIPStephan

And that’s the dialog where I can’t even use Cmd-D (or any keyboard shortcut) on my German Mac.

I’m pretty sure they are considering everything that’s feasible, we don’t have to tell them. It’ll just not be done right away but when it’s ready.

This sounds like Windows, though. I’m talking about macOS. Yeah, I think the OS language is the culprit here (and I think the devs told me that already) but it’s not an excuse. As I said, it works in every other program, just not in AD. And in LibreOffice I can at least hit Cmd-N for “Nicht speichern”, but their interface doesn’t look very Apple-like anyway (because it’s not originally developed for Mac, just ported afterwards, I think).

But what is “sufficiently good” and when is it reached? My point is that either you implement it properly with all the consequences or not at all. If you start with simple 3D functionality but leave out related things (e. g. lighting) then people are gonna be disappointed and say AD is just half done. I think 3D is something for a separate application (as there are already) – it could, of course, interact with AD’s current functionality (much like AD can interact with AP already, and both of them will be able to interact with APub in future) but should probably not be implemented as part of AD because that would open a whole nother can of worms for the developers (I’ve said the same thing about HTML/CSS export and prototyping tools).

Wouldn’t implementing some halfhearted 3D functionality cause exactly that problem? People would start with AD thinking they can do 3D modelling and then discover that a lot of necessary things are missing and would be more disappointed than if they had known beforehand that AD is not a 3D tool.

I’ve brought this up before (but can’t find it anymore) and it has been kind of waved aside by staff but new observations have me bring this up again: I’m used to hit Cmd-D when the modal dialog comes up to dismiss unsaved work. This works with every program except Affinity Designer (and LibreOffice but that’s a different subject). I have to add that my OS language/locale is set to German but still, the shortcut is universal and works in every program I can think of right now except this one. Now, I don’t remember what Serif staff told me would be the reason for that but interestingly I can use the keyboard shortcut Cmd-R for “Replace file” in the respective dialog box when saving a file with the same name as an already existing one. So, why is that? I find it a major inconvenience that I can’t dismiss unsaved work with a keyboard shortcut.

A very German word order.

Yeah, no. That would open a whole nother can of worms. And the intricacies of this have been discussed in many other threads before.

@TonyB, perhaps it would be a good idea to strike out the items that have been implemented rather than just removing them from the list? This way we see the progress that has already been made and people might not ask for this and that everytime?

No.

Right, sorry; for a moment I forgot we’re already in the feature requests forum because of the extended talk about Adobe. All is good, forget that suggestion by me.

Neither do I and neither is it for me which brought me to Affinity, too. Of course Adobe wants people to switch to the subscription model, just as any company wants people to upgrade their software to the newer version while older versions aren’t supported anymore (or barely get basic fixes). That’s progress and one can’t stop it (at least when you’re upgrading a component (the OS) on which another component (the program) relies). The best thing you could do is open a feature request for JPEG2000 support, and in the meantime use GraphicConverter to convert all your files which, according to Wikipedia, can handle JPEG2000 (but then, if you’ve converted everything you probably don’t need JPEG2000 support in AP anymore, haha).

I know that Fireworks CS5 is requiring the Java 6 runtime environment in order to work; I had to specifically install that when I upgraded to El Capitan. I could imagine this to be similar with older versions of other Adobe software. So, I wouldn’t really put the entire blame on Adobe, it could very well be that at the time of development that runtime environment was state of the art and with newer versions of their software they also switched to newer versions of the runtime environment, but it would be a waste of resources to port the old verisons over, too. And newer versions of the operating system (in this case by Apple) just don’t support the old runtime environments anymore.

Sorry for chiming in when I have no idea about anything here, but I wanted to expand on the greyed out file name in the Open dialog: you could try to context-click a JPF file in Finder and select “Open with”, and then, if AP isn’t shown in the list, select “other app…” (or whatever it says in English; it’s the option at the very bottom in the context menu) and select AP from there. Alternatively you can drag a file onto the application icon in the dock. And yet another alternative would be to open the info window (Cmd-I) of a selected file and set the program to open the file from there (under “open with”).

How do you know that there won’t be 2.10 and so on (and likewise 1.10 etc.)?