Bug 390950 - Support fractions for size and position of vector objects
Summary: Support fractions for size and position of vector objects
Status: RESOLVED DUPLICATE of bug 466582
Alias: None
Product: krita
Classification: Applications
Component: Layers/Vector (show other bugs)
Version: git master (please specify the git hash!)
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-23 14:13 UTC by Vladimir Savic
Modified: 2024-01-22 08:11 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Video that demonstrate where to look (3.01 MB, video/ogg)
2018-02-23 14:13 UTC, Vladimir Savic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Savic 2018-02-23 14:13:39 UTC
Created attachment 110936 [details]
Video that demonstrate where to look

I've attached video that demonstrates the problem. In short, you are able to enter decimal values in Tool options dialog, but as soon as you submit them (by pressing Enter) they show rounded value, even though on-canvas presentation stays correct - represents the values you've entered.

Not really the best demonstration, but you will figure it out.
Comment 1 wolthera 2018-02-23 14:19:18 UTC
Hm, that's proly because it's a bit silly to have floating point values for pixels.

I guess in the situation that the user input floating point values into the docker, we should switch to the actual vector unit: pt, or we should allow floating point pixel values.
Comment 2 Vladimir Savic 2018-02-23 14:31:39 UTC
I would propose allowing frictions of a pixel in input field. That is not so uncommon in vector editing software. You would need that either way if you want crisp edges on for example 3px wide stroke.

The second solution is to actually sync what is on canvas with exact values entered in input widget. This is a solution I don't favour because it limits a workflow in some cases (see above).
Comment 3 Tiar 2020-12-11 19:50:08 UTC
*** Bug 416833 has been marked as a duplicate of this bug. ***
Comment 4 Tiar 2024-01-22 08:11:57 UTC

*** This bug has been marked as a duplicate of bug 466582 ***