Friksel Posted December 18, 2019 Posted December 18, 2019 When setting a stroke width below zero, the textbox shows this when it's above 0.1. So widths like 0.2, 0.3, 0.123 are shown as expected. But when the width is below 0.1 Affinity suddenly acts like there is no border at all; it shows zero instead of the real value. I'm using widths below 1 a lot for digital animation work (using svgs), like zoom in animations, also widths with values below 0.1. So for the work I do this is a pretty common scenario I bump into many times. And when widths are below 0.1 there's no way in reading somewhere in the user interface there is in fact a width (not zero) and what that value currently is set to. This is what we see now when the strokewidth is below 0.1, which is obviously telling us users there is no width, while in fact there is: I understand developers don't want to show all digits and have to deal with rounding the real values, but truncating to zero is just not right. Why not display '< 0.1' instead so the user can see there is in fact some width so not zero. Than when a user hovers over the width slider or the textvalue inputbox with a pointer it can show the real, full number of the width, in a tooltip so we can always see what value the width is really set to. Like this: it shows '< 0.1' if the value is below 0.1 and when the user hovers it shows the real/full value: I don't believe this is a lot of work to build in the software, but it would definitely help communicating to us users a lot better (and not confusing in acting like the border is zero, when there is a border set). [edit] I see now I accidentely posted this in the publisher forum, although it was meant to be in the Designer forum. I leave it like this because it affects all three programs anyway. Quote
walt.farrell Posted December 18, 2019 Posted December 18, 2019 You need to go to Preferences, User Interface (UI), and adjust the number of decimal points displayed for values displayed in points. It defaults to 1, where anything from 0 to .05 would round down to 0, and anything from .05 to .099 would round up to .1. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
carl123 Posted December 19, 2019 Posted December 19, 2019 11 hours ago, Friksel said: So widths like 0.2, 0.3, 0.123 are shown as expected. That would suggest you have set your decimal points to at least 3 decimal places. Is that correct or is the above a mistake? 10 hours ago, walt.farrell said: It defaults to 1, where anything from 0 to .05 would round down to 0, and anything from .05 to .099 would round up to .1. A small correction... "It defaults to 1, where anything from 0 to .04 would round down to 0, and anything from .05 to .09 would round up to .1." walt.farrell 1 Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
Friksel Posted December 19, 2019 Author Posted December 19, 2019 12 hours ago, walt.farrell said: You need to go to Preferences, User Interface (UI), and adjust the number of decimal points displayed for values displayed in points. It defaults to 1, where anything from 0 to .05 would round down to 0, and anything from .05 to .099 would round up to .1. Thanks @walt.farrell. Never knew about that setting. That helps a lot indeed! Quote That would suggest you have set your decimal points to at least 3 decimal places. Is that correct or is the above a mistake? @carl123 Obviously the way the software is build now we should. It would be nice if we didn't need to, because 0.2 doesn't have to be written as 0.200, but I understand the precision float number problem and I think the solution to make users pick the precision themselves is not bad at all. The only thing I still think is strange is that when a value is rounded to zero the textbox doesn't give users any clue that the value isn't zero. In my opinion zero is a special case, because when setting a border to zero that implicates that there is NO border at all and having no borderwidth would result in no border export either. So if I were Affinity I would handle the zero differently and add some indication in the UI that the value is not exactly zero, but rounded to zero in the display only. Like showing an asterix after the value textbox or something, to indicate that the value is not exactly zero, but a small number, rounded to zero. '0 px' * But we can't have everything and being able to set the decimals ourselfs helps a lot. Thanks again @walt.farrell ! Great tip! walt.farrell 1 Quote
R C-R Posted December 19, 2019 Posted December 19, 2019 7 hours ago, Friksel said: The only thing I still think is strange is that when a value is rounded to zero the textbox doesn't give users any clue that the value isn't zero. True, but the stroke Style icon buttons to its left does do that. The first one (the circle with the red slash) won't show as selected if the stroke has any non-zero width, even if it is 0.00001 px. Quote All 3 1.10.8, & all 3 V2.5.7 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7
Friksel Posted December 21, 2019 Author Posted December 21, 2019 On 12/19/2019 at 5:00 PM, R C-R said: True, but the stroke Style icon buttons to its left does do that. The first one (the circle with the red slash) won't show as selected if the stroke has any non-zero width, even if it is 0.00001 px. That's not true. Try putting the strokewidth to 1px: you see the stroke buttons are automatically switched to the line-icon to indicate there is a stroke now. But when setting the stroke back to 0px after that, it never switches back to the non-stroke iconbutton. So there's no way to tell than if the stroke is 0px or 0.00001px. If this would work as you described and therefor as expected, that would indeed be a nice addition to the interface to be able to tell if there is a border or no border width. But it's obviously not working at the moment. So just filed a bug: Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.