Oval
Members-
Posts
2,181 -
Joined
Everything posted by Oval
-
Affinity Designer Customer Beta (1.6 - Beta 8)
Oval replied to MattP's topic in [ARCHIVE] Designer beta on macOS threads
The corrected version (1.6.0.57) still does not work for some users: -
Affinity Designer Customer Beta (1.6 - Beta 8)
Oval replied to MattP's topic in [ARCHIVE] Designer beta on macOS threads
Sorry for asking, but is this possible with that unusable empty preference panel or is there a different trick next to reinstalling the old beta (or deleting files)? -
Some users might think that you can only create new topics in the subforums. See an example: So would a different arrangement of “Start new topic”/layout be possible, please?
-
Some users might think that you can only create new topics in the subforums. See an example: So would a different arrangement of “Start new topic”/layout be possible, please?
-
Affinity Designer Customer Beta (1.6 - Beta 7)
Oval replied to MattP's topic in [ARCHIVE] Designer beta on macOS threads
Hm, we understand this. So wouldn’t it be better to ask for single reports (in future)? BTW: But there are also old threads that are without reaction. -
Affinity Designer Customer Beta (1.6 - Beta 7)
Oval replied to MattP's topic in [ARCHIVE] Designer beta on macOS threads
No crash but this (second line). HTH -
Thanks. Sorry, just wanted to be clearer if the English was not good enough. Do the changed functions get a quality inspection before they are put online (since the beta 6 “Expand Stroke” has a new issue)? Your misinterpretation.
- 20 replies
-
- expand stroke
- bugs
-
(and 1 more)
Tagged with:
-
Affinity Designer Customer Beta (1.6 - Beta 7)
Oval replied to MattP's topic in [ARCHIVE] Designer beta on macOS threads
Bitte, wurde der Dezimaltabulator-Bug, auf dessen Korrektur Nutzer seit über einem Jahr warten, auch bereits »logged to be solved«? Das Problem betrifft wohl u. a. Albanien, Andorra, Argentinien, Belgien, Bolivien, Brasilien, Bulgarien, Chile, Dänemark, Deutschland, Ecuador, Estland, Färöer, Finnland, Frankreich, Georgien, Griechenland, Grönland, Indonesien, Island, Italien, Kolumbien, Kosovo, Kroatien, Kuba, Lettland, Litauen, Luxemburg, Mazedonien, Moldawien, Niederlande, Norwegen, Österreich, Paraguay, Peru, Polen, Portugal, Rumänien, Russland, Schweden, Teile der Schweiz, Serbien, Simbabwe, Slowakei, Slowenien, Spanien, Südafrika, Tschechien, Türkei, Ukraine, Ungarn, Uruguay, Venezuela, Weißrussland und indirekt alle Länder. -
Affinity Designer Customer Beta (1.6 - Beta 7)
Oval replied to MattP's topic in [ARCHIVE] Designer beta on macOS threads
This fourth problem with “Expand Stroke” is since the algorithm in beta 6 produces too few nodes: -
Serif wrote “may require a complete rewrite or a different approach to get solved”. The context here is the topic of this thread. It is about “Expand Stroke”, not about the whole app. We did not write “the entire base of the app”. It is perfectly logical that you do not have to rewrite the whole base (including colours and text features) of the app to get a flawless “Expand Stroke”.
- 20 replies
-
- expand stroke
- bugs
-
(and 1 more)
Tagged with:
-
Just an example to explain the view of some professionals. The app is “created for professionals” and Serif claims “most precise vector graphic design software available”. If you work for horology as a pro like lenogre—to get back to the topic of this thread—you can run into trouble, because sometimes “expand stroke” is imprecise (criticized for years). If the result was produced in a high number of copies for an exhibition, the pro not only loses one customer, because people are not satisfied with the quality. We understand that some “average users” are very satisfied but also that some professionals (that must rely on the promised precision etc.) sometimes are disappointed.
-
Affinity Designer Customer Beta (1.6 - Beta 7)
Oval replied to MattP's topic in [ARCHIVE] Designer beta on macOS threads
@MattP Seems to bump into big public interest. If you would be more specific, we would be glad to answer. It was not an easy job (because the search lacks a previous feature), but a more-than-normal level of negativity was not found in this thread. Maybe we interpret smileys differently or misunderstood something. Hm, what exactly is too badly formulated, what should be corrected? Should we thank Serif every time for our bug report and for helping other users or simply stop our work that’s not the industry-standard? Language barrier thing? Meant seriously: Shouldn’t your first sentence end with a question mark or is it not a question, please? -
Affinity Designer Customer Beta (1.6 - Beta 7)
Oval replied to MattP's topic in [ARCHIVE] Designer beta on macOS threads
Double-click on a handle of a single-segment straight line results into something like a non-existent curve. Same behaviour: mid handle of frame text. Sometimes the same happened when single-segment straight lines were scaled using the transform panel. -
Affinity Designer Customer Beta (1.6 - Beta 7)
Oval replied to MattP's topic in [ARCHIVE] Designer beta on macOS threads
Yes, thank you Serif for ignoring German purchasers in this point comma. -
We can understand that professionals claim “it is created for professionals with the claim to be the fastest, smoothest, most precise software available but some needed features are not usable because they are not corrected since years”.
-
Affinity Designer Customer Beta (1.6 - Beta 7)
Oval replied to MattP's topic in [ARCHIVE] Designer beta on macOS threads
Perhaps very very few users have problems because the tab stop with decimal alignment still does not work in German. -
Perhaps it makes sense if Serif always would explain why “very soon” promised (and since years missing) features / corrections did not make it into the new beta. Could avoid disappointment.
-
For example the Affinity factor “very soon” that corresponds very precisely to three years.
-
Practical experience with stroking cats is appreciated.
-
If Serif really interprets that the whole codebase including parts like text and colour algorithms must be rewritten because of issues of “Expand Stroke”, you have to be scared as user.
- 20 replies
-
- expand stroke
- bugs
-
(and 1 more)
Tagged with:
-
Crazy (?!), but Serif claimed: “may require a complete rewrite”. Because issues of a basic function were not corrected within years, this explanation is a logical one. Also, after three years users could get the impression they must use this function forever in other programs.
- 20 replies
-
- expand stroke
- bugs
-
(and 1 more)
Tagged with:
-
Seems this is the reason why GraphicConverter has a reference manual (more than 300 pages) for the wide scope and Affinity Designer never had such a manual. mac_heibu just asked for a name of a different software product, which is developed faster, which we gave to him. We just wanted to be helpful. If it actually was so important for some developers to discuss this comparison, we could name a bigger and quicker developed app than AD. Just ask. But again: We don’t need and did not start those comparisons and “file converter” an insulting term for for GraphicConverter. It has many features that we use because they are missing in the Serif “graphic design package”. For example some DAM and photo editing features.
-
A function that is needed every day a lot and we had those fears for more than two years. Sorry!
- 20 replies
-
- expand stroke
- bugs
-
(and 1 more)
Tagged with:
-
lenogre wrote “development seems slow down”, not that others are faster! A comparison certainly does not help his concern, but here is one product for mac_heibu: https://www.lemkesoft.de/en/products/graphicconverter/overview-of-new-features-and-versions/ One man show and he resolved complex wishes within 24 hours without a bug.
