-
Posts
9,038 -
Joined
-
Last visited
Everything posted by Pšenda
-
publisher move files
Pšenda replied to namron006's topic in Affinity on Desktop Questions (macOS and Windows)
-
My Brush is Acting Weird
Pšenda replied to dwr7eleven's topic in Affinity on Desktop Questions (macOS and Windows)
-
These Expand Stroke errors often occur when placing two Nodes on top of each other, or when the curve is unnaturally curved. Try to provide the same screenshots with the selected Node Tool.
-
A common technique is to (optionally) store an index backup file with an optional number of indexes. It is thus up to the user to choose between the storage speed or its safety, when he always has several backup files available.
-
You don't mention the problem with two layers in your initial post ("3. Move layer only to a new position."). However, moving with two layers makes no difference. Of course it could be an OS difference issue, but it's always good to confirm or deny. Try the same procedure with "move layer to new position" (your description was a bit vague) and see if the bug is related to your OS.
-
Outline on transparent Object
Pšenda replied to DarkClown's topic in Affinity on Desktop Questions (macOS and Windows)
Interestingly, this option doesn't work properly because an ellipse with No Fill and No Stroke settings (or 0% opacity) is definitely not "visible". So the wording should rather be - objects with enabled Visibility 🙂 -
Level out color
Pšenda replied to StevieDesigns's topic in Affinity on Desktop Questions (macOS and Windows)
If you want to keep the maximum from the original scan, including its inaccuracies, but which make its more authentic, I recommend using a blue brush with a soft edge, and just iron the "spotty" areas a little and unify them. -
Escape key's function
Pšenda replied to Pieter van Wyk's topic in Feedback for the Affinity V2 Suite of Products
But the Move Tool is also a tool. So should there be a release to the Hand tool? Nothing can be done/caused by it except for moving the canvas/document. -
As far as I know, Lightroom uses the SQLite database format, the characteristics of which are known as "ACID" (Atomic, Consistent, Isolated, and Durable), that is, it is resistant to data storage errors. This format uses a similar way of storing new/changed data as Affinity, where records are compressed only after reaching a certain limit of unused space, or on demand - the VACUUM command, see my previous link.
-
In the case of standard file sizes, i.e. on the order of hundreds of megabytes to units of gigabytes, this is a negligible effect. But if you work with really large files (ideally to external drive or with NAS :-), then the effect will be enormous. Therefore, this method of incremental storage is a standard technique, for example for database files. I once requested a feature that would compress a file on demand - unfortunately it didn't even seem to be understood.
-
Which master page is being used?
Pšenda replied to LondonSquirrel's topic in Feedback for the Affinity V2 Suite of Products
-
Export preview wrong for unsupported properties
Pšenda replied to NotMyFault's topic in V2 Bugs found on macOS
Some "rat" crept in there 🙂