IthinkthereforeIam
-
Posts
18 -
Joined
Posts posted by IthinkthereforeIam
-
-
58 minutes ago, v_kyr said:
It's not always wise to communicate all those things ... most feature demanding users also don't have any real clues about development procedures, it's complexity (difficulty levels 1-12), possible unwanted sideeffects, needed format changes and the general impact for certain demands here. So what can be realistically done fast and painless, in contrast to very complex (possible more error prone) extensions.
... operating algorithm is also no trivial task. ... And so on ...
Thus I said, it always depends.
Or according to Murphy's law (which is an aphorism about human error or sources of error in complex systems) which states: “Anything that can go wrong will go wrong.” 😉
You're right, it's never easy to communicate (at all levels) and indeed, I remember reading on more than one occasion that adding such a feature was "the simplest thing to do, and that it should be so easy that it should already be done!"... I talk enough with developers (my sons) to realise that it's clearly not simple to add a new feature to a program that has already become so complex. In fact, they say that it's not normal for a program (or part of) to work straight away 🙂
-
27 minutes ago, v_kyr said:
It always depends. - If many users always mostly ask after one specific feature, then it gives some insight about a certain feature demand. Then its implementation will probably be given a higher priority as long as it can be done quickly and is not too complex and time consuming.
Maybe, but some features have already been requested so so many times that I'd be very surprised if they were to learn again that such a distinct tool would be much appreciated by some, that better table management is essential or global layers or... etc. etc....
Incidentally, I re-registered to download one resource and my first impression after more than a year and a half was that communication had improved between Serif and the users. In fact, the apparent structuring of bug reports and their follow-up has improved (a definite advantage for the company too), but users are not yet entitled to a short/mid/long-term vision of the evolution of the suite's apps. So there's still the uncertainty of what's to come, and therefore all these incessant repeated requests (which also make reading the forum tiresome sometimes/often and on the whole, not very informative... as is this thread for the majority of users 🙃). -
12 hours ago, R C-R said:
I'm sure Serif does care but as has been mentioned, they do not have enough resources to implement every feature various users might want -- there are at least several dozen of them that different uses believe should be considered "major" ones, & many different & often conflicting ideas about how they should be implemented.
Just browse a bit through the Feature request sub-forum to get an idea of all the different things people have asked for.
You're right: the lists of bug reports and requests for improvements are indeed impressive, but it's always been like that for as long as I can remember. It can't be easy to maintain a software suite on different OS, and expectations have always been high for enthusiasts/hobbyist to be able to have fun/work at lower cost without a subscription.
However, I don't think user requests are a high priority. It's almost a commonplace to say that they know very well at Serif what should be implemented to improve their apps, and I assume they have an internal long-term/timeline plan based on their ability to carry it out. I think it's really pointless to keep asking ad nauseam this particular obvious feature, or another one, etc.
-
5 minutes ago, walt.farrell said:
I suppose our definition of "major" may differ, but there has been, in my opinion, a lot of new functions added to V2 in the 2.1, 2.2, and 2.3 (and soon 2.4) releases.
https://affinity.serif.com/en-us/whats-new/
"may differ" indeed and I have no doubt about your wisdom and the sincerity of your thoughts... I did add "in my humble opinion" and I'm not on this forum to start new endless polemics about what was or should be. Thanks but no...
-
4 minutes ago, v_kyr said:
Well I believe, there are actually so many urgent bugs to fix in v2 (add to that all existing so far not fixed from v1) that they probably don't have yet the time to enhance specific app features. OR in other words, as far as some existings, interdependent, internal bugs for certain functions aren't fixed, it won't make much sense to enhance certain features, as you then would carry over old ones and introduce then additional new bugs. - What I mean here is, if you have a fault free basic framework and features implementation, then it's much easier to work on/with that, as you then have the time to enhance things and enhance & add features.
All in all certain things have always to be prioritized and adding the capability for sharable subcategories between categories is probably not yet on the top of their todo stack.
What you write makes sense if there are still so many bugs in v2. This would also explain the lack of major development and optimisation since the v2 release IMHO.
I agree that the property of exchanging subcategories that I raised is of little importance. One problem is that you can't open several categories at the same time (so I assume this remains true for v2) and that what you've set up in one category can't easily be integrated into another unless you perform some time-consuming deconvolution (duplicating, deleting, exporting, reimporting, whatsoever...).
-
29 minutes ago, v_kyr said:
Nope, as I initially said, there have been nothing added/done in this direction.
The ability to define assets is really useful, especially when combined with symbols. I've just had a quick look at the new features in v2. Sometimes I get the impression that Serif stops halfway between interesting features and really optimized ones but that's just my perception (& I know, Serif doesn't care) 🙂
-
9 hours ago, walt.farrell said:
And in particular, from the 2.1 enhancements in that What's New list:
Thank you for finding this info. Still no sub-category exchanges, then.
-
23 minutes ago, v_kyr said:
... it would have been mentioned in some version changes thread.
very probably, but I haven't followed the development of the apps or resumed diligent reading of the forum.
-
2 hours ago, v_kyr said:
..., no that's AFAIK not possible (...at least not in v1 apps).
I know for v1, I was wondering whether there was any improvement in assets management in v2. Thanks.
-
I sometimes still have to use AD v1 for editing old schemes and I was wondering how assets are managed in v2?
I've gone through the online help and there are categories and subcategories. I understand that only categories can be exported and imported. I don't see any indication that subcategories can be exchanged between categories. I assume that it isn't? Thanks for confirming this 🙃 -
Just as a touch of humour, here's a photo I found edited with APh v1 some time ago, just modified for the occasion (text & liquify applied to the head):
- TheSnooze, TrentL and jmwellborn
-
3
-
Interesting question. I don't use APhoto v1 (because of lag issues) and I was wondering whether v.2 handles nef raws well, including those of the Z8 I'm looking at (or the future z7III).
-
5 minutes ago, bbrother said:
I don't think this will happen (public roadmap) for several reasons such as:
- Plans often change during the ongoing development
- Roadmap gives to much information to other companies.
- User complaints when the roadmap changes
Despite all the inconvenience of a public roadmap, I believe they would benefit more if it were available. What exactly would they gain:
- They would gain more trust (priceless),
- By involving users, they could better manage the process of reporting features that users would like to see implemented
- Fewer dissatisfied customers. More conscious decisions and users, less reasons to complain.
A pity, but their choice...
And I agree that it would bring more benefits. -
22 minutes ago, Bit Arts said:
It's crazy that Affinity Designer doesn't have this incredibly time-saving and useful feauture, so I can't imagine it not being implemented at some point.
Amadine is a really nice application for macOS, iPadOS and even iOS, so you can actually stand in a crowded subway train in Japan and still use this feature even on your iPhone. It works perfectly on a regular iPhone and the stroke can be adjusted like a breeze with your thumb on the mobile screen! Now that's the result of true user interface customisation and specialist involvement.
So the company behind it - unlike Serif unfortunately - has actually devised a special, space-saving tablet and mobile interface. And of top of it implemented path width control.
If Serif gives no indication of what will be implemented, customers can only wait hoping that maybe... I work on a PC and use VectorStyler more and more, which is also incredibly feature-rich, and am eagerly awaiting the new version to integrate it permanently into my work and workflow.
-
On 4/7/2023 at 1:11 AM, earl_grey said:
I would like to suggest adding a Path Width Tool for easier and more precise stroke adjustments. This tool would allow users to thicken the outline at specific points by simply clicking and dragging with the mouse. Other software like Adobe Illustrator and Amadine have a stroke width tool.
The current method, using the Pressure chart in the Stroke panel, is not as user-friendly or accurate as it could be.
Totally agree. I remember that this feature was already requested many many times during the development of v1... so there's still this little frame that's difficult(impossible) to use for complex variations in stroke thickness. And it's still impossible to know whether Serif wanted to bring this, I suppose.
-
1 hour ago, Patrick Connor said:
Welcome to the forums, and thanks for your kind and positive comments
@Patrick Connor Thank you for your welcome post
You're right to take a positive view of my post, it must be... but you're not getting involved in any response whatsoever (regarding the roadmaps). In any case, I'm no longer holding my breath (with Serif), so maybe it'll come to that.
-
1 hour ago, Patrick Connor said:
It's our current approach, we did the same for 2.3 I think, and we'll try to continue going forward. It should lead to fewer regressions
To Serif (Patrick Connor): former v1 & forum user (and still sporadic AD v.1 user) and back on the forum after a long (?) time, it seems to me that you have somewhat improved the communication between you(i.e.,Serif) and the users of your apps, it wasn't too difficult because there was almost no communication before version 2... If you wish to continue in this direction, have you (or could you) discuss internally the possibility of reintroducing a roadmap for the 3 apps? I'm not a v2 user yet, but it would help me in my choice of a professional workflow. As I haven't been on this forum for a while, I'm sorry if the question has already been asked again & again &...
BR,
Patrick
How do you set priorities?
in Beta Software Program Members Area
Posted
I'm procrastinating and browsing a few threads. I hope you don't mind I'm commenting on your post. I don't want to seem obsessed with a public rodmap, but I don't quite understand the rationale for not revealing a draft of the new features for the next few releases. You're at beta 2.4, so you could mention what the developers are working on for say the next two or three versions (making it clear that you're not bound to these roadmap previews).
If you're still a long way from v.3, you could even consider a longer-term roadmap, without compromising your primary objective of selling licenses... so you may avoid a fraction of repeated requests for new features, questions for knowing what is coming next, etc. 🙂 I think you'd rather read a good novel (or even Shakespeare's classics) than numerous posts on this forum (new spiral tool : 😵💫)