nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Improve consistency of 'use fractional characters' toggle in scalebar settings

wayfaringrob

I've noticed that the 'use fractional characters' toggle does not always convert fractions such as 0.25 and 0.5 to fractions. With my division value set to 0.5, it works, but when I set my division value to 0.25, they still appear as decimals.

I don't know if it's related, but when setting the division value to a decimal, if you don't include a leading 0 when typing it, it glitches. Entering something like '.25' shows up as '50.2' for some reason.

Not sure if this is a feature or a bug but I would prefer to have fractional characters appear when possible if I've got that toggle on.

Find more posts tagged with

Layout

Closed

Status: Closed

Comments

AubriOtis

Thanks for reporting! This looks like a bug in the software, not an idea for new functionality. The ideas site is for reporting new ideas, we don't want to have bugs here, but rather in a system where they can be troubleshooted and reported to the appropriate team quickly. Bugs don't need to be voted on, they are functionality that should work but don't. I recommend reaching out to tech support directly so they can log a bug you can follow. If you would like this also available on Esri Community to hear about potential workarounds from fellow GIS people, you can re-add it as a post. Thanks!

-Aubri

wayfaringrob

@AubriOtis that's what I thought, thanks! On that note, it would be swell if there were a smoother mechanism for reporting bugs, similar to Ideas or even within the software like MS products. Logging bugs through tech support is a bigger hassle than it's worth which is one of a few reasons I start here. The other reason is that I'm often told in the end that the bug I spent time and energy on reporting (phone calls, screen shares, emails) is actually considered a "feature" and there's nothing they can do. If it's going to be this difficult to report all that is broken, users are not going to. Most of my friends & colleagues know very well the overly buggy nature of ArcGIS products but just assume that it's the way things are and there's nothing they can do about it, and as someone who does report these things, I see their reasoning and I also often just ignore bugs rather than reporting them. Making it easier & more evident for users to report these issues would be a win-win for everybody.