Skip to content

Custom format for the crosshair mark? #1596

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mbostock opened this issue May 19, 2023 · 5 comments · May be fixed by #1597
Open

Custom format for the crosshair mark? #1596

mbostock opened this issue May 19, 2023 · 5 comments · May be fixed by #1597
Labels
enhancement New feature or request

Comments

@mbostock
Copy link
Member

The crosshair mark doesn’t currently provide an option to control how the values are formatted. The text channel in constructed using an initializer. Maybe it needs a format option, but we’d need separate options for x and y?

@mbostock mbostock added the enhancement New feature or request label May 19, 2023
@Hvass-Labs
Copy link

Same problem for the tip / pointer. In my case I would just like it to use the tickFormat I have already set for the given axis. Thanks!

@sk31park
Copy link

K-009

I want format option.
Because I want change date format like 'YYYY-MM-DD hh:mm' in crosshair X label..

@JakeShirley
Copy link

I would love it, as I am trying to make my charts have relative time scales with a custom tick format and this crosshair label is just silly compared to it
image

@fernhaven
Copy link

I would like to be able to apply a format to the crosshair text for x and y so that the text that shows up with the crosshair matches the formatted labels on the axes.

@gvanhorne
Copy link

Are there any examples of implementing a custom cross hair with the pointer transform and text mark as suggested by the docs? I've been searching around and coming up empty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants