Add thousands separators to scene stats #38898

Closed
opened 2014-03-01 05:28:20 +01:00 by Diego Gangl · 22 comments

This patch adds a thousands separator to the stats in the info header so they are more readable.

thousands.png

thousands-separator.patch

This patch adds a thousands separator to the stats in the info header so they are more readable. ![thousands.png](https://archive.blender.org/developer/F79306/thousands.png) [thousands-separator.patch](https://archive.blender.org/developer/F79308/thousands-separator.patch)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Diego Gangl self-assigned this 2014-03-01 05:28:20 +01:00
Author

Added subscriber: @Januz

Added subscriber: @Januz
Diego Gangl was unassigned by Bastien Montagne 2014-03-01 13:04:51 +01:00
Brecht Van Lommel was assigned by Bastien Montagne 2014-03-01 13:04:51 +01:00

Added subscribers: @brecht, @mont29

Added subscribers: @brecht, @mont29

I’m not sure we want to add such thing (in this case, we would also need it for any num button), not convinced it’s worth the added complexity.

Assigning to @brecht, he’s our UI chief!

I’m not sure we want to add such thing (in this case, we would also need it for any num button), not convinced it’s worth the added complexity. Assigning to @brecht, he’s our UI chief!

Added subscribers: @JonathanWilliamson, @billrey, @ideasman42

Added subscribers: @JonathanWilliamson, @billrey, @ideasman42

If this is accepted, would like the function to be generalized and added to BLI_string.h.

I don't have a strong opinion on the patch, it can be hard to tell how many faces you have at a glance when you get over 100,000 - 1 milllion.

If this is accepted, would like the function to be generalized and added to `BLI_string.h`. I don't have a strong opinion on the patch, it can be hard to tell how many faces you have at a glance when you get over 100,000 - 1 milllion.

I think this is useful, it's difficult to see now if you have 1 million or 10 million faces now.

It could be done in number buttons too but doing it only here is already an improvement. In number buttons you usually don't have to type such bigger numbers, if you do it's likely bad UI design or a case where units would help, so I wouldn't worry about that case.

I think this is useful, it's difficult to see now if you have 1 million or 10 million faces now. It could be done in number buttons too but doing it only here is already an improvement. In number buttons you usually don't have to type such bigger numbers, if you do it's likely bad UI design or a case where units would help, so I wouldn't worry about that case.
Author

@mont29 thanks for re-assigning, I wasn't sure what to put there :P

stats_format() could be moved to BLI_string. However, one issue is that it's using locale.h to get the locale's separator, maybe it should use blender's methods (iface, etc.)?

About number buttons, the only big numbers I can see are the particles count and the blackbody node. Not sure it's worth it.

@mont29 thanks for re-assigning, I wasn't sure what to put there :P stats_format() could be moved to BLI_string. However, one issue is that it's using locale.h to get the locale's separator, maybe it should use blender's methods (iface, etc.)? About number buttons, the only big numbers I can see are the particles count and the blackbody node. Not sure it's worth it.

the separator could simply be passed as an argument.

Though not sure how important it is to support, and by the looks of it only ascii separators are supported anyway. so it could just be hard coded to use ,.

We don't use locale for number display either.

the separator could simply be passed as an argument. Though not sure how important it is to support, and by the looks of it only ascii separators are supported anyway. so it could just be hard coded to use `,`. We don't use locale for number display either.

I believe this is a good change. It makes things more readable and is particularly relevant in the INFO bar as those are all report numbers, not necessarily settings.

I believe this is a good change. It makes things more readable and is particularly relevant in the INFO bar as those are all report numbers, not necessarily settings.

Added subscriber: @scottyp

Added subscriber: @scottyp

I like this! +1. I can't speak for how it is implemented in the patch, but adding commas makes large numbers easier to read. It would be nice if this would carry over to make it more global, but that might be too much work for now.

I like this! +1. I can't speak for how it is implemented in the patch, but adding commas makes large numbers easier to read. It would be nice if this would carry over to make it more global, but that might be too much work for now.

Added subscriber: @DavidSisco

Added subscriber: @DavidSisco

Alternative suggestion here.
What if we just start abbreviating "million" to the end if the number goes above 999,999.
Eg: instead of "10,528,000" it would show "10.5 million".
That might be even more easily recognizable at a glance.

Though that would add the issue of "what if you actually want to know exactly how many are there".
Food for thought.

Alternative suggestion here. What if we just start abbreviating "million" to the end if the number goes above 999,999. Eg: instead of "10,528,000" it would show "10.5 million". That might be even more easily recognizable at a glance. Though that would add the issue of "what if you actually want to know exactly how many are there". Food for thought.
Author

@DavidSisco The issue with "10.5 million" is that any change below 100,000 would go unnoticed, and that's a lot of faces/verts.

New patch! with stats_format moved to BLI_string. The separator is now hardcoded with a reminder to fix it in the future.
thousands-separator2.patch

@DavidSisco The issue with "10.5 million" is that any change below 100,000 would go unnoticed, and that's a lot of faces/verts. New patch! with stats_format moved to BLI_string. The separator is now hardcoded with a reminder to fix it in the future. [thousands-separator2.patch](https://archive.blender.org/developer/F79673/thousands-separator2.patch)
Author

Rebased so it applies again.
(Should I post this in differential instead?)

thousands-separator-3.patch

Rebased so it applies again. (Should I post this in differential instead?) [thousands-separator-3.patch](https://archive.blender.org/developer/F97749/thousands-separator-3.patch)

Yep, would be good to make a differential, otherwise its hard to give feedback.

Yep, would be good to make a differential, otherwise its hard to give feedback.
Author

Added Diff D646

Added Diff [D646](https://archive.blender.org/developer/D646)
Author

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Author

Patch commited, closing this.

Patch commited, closing this.

Added subscriber: @dbrgn

Added subscriber: @dbrgn

I'm not sure if this is the right place for discussion (especially as this is closed), but some places are still missing the separator, e.g. the face count in the decimate modifier:

20150228_210316.png

Any plans to add the separators there too?

I'm not sure if this is the right place for discussion (especially as this is closed), but some places are still missing the separator, e.g. the face count in the decimate modifier: ![20150228_210316.png](https://archive.blender.org/developer/F146388/20150228_210316.png) Any plans to add the separators there too?
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#38898
No description provided.