Skip to content
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

Listen to more plots properties on selected and click events #2059

Open
1 of 6 tasks
ShootingStarD opened this issue Oct 15, 2024 · 3 comments
Open
1 of 6 tasks

Listen to more plots properties on selected and click events #2059

ShootingStarD opened this issue Oct 15, 2024 · 3 comments
Labels
🖰 GUI Related to GUI ✨New feature 🟨 Priority: Medium Not blocking but should be addressed

Comments

@ShootingStarD
Copy link

ShootingStarD commented Oct 15, 2024

Description

I just stumbled across the dash documentation regarding selection here. Here they have a very useful features which allows to also capture the custom_data , that is data that we add to the points plotted. It can be used so that the developer add index of rows in the custom_data (very easy with plotly express hover_data argument) and then the developer of the dash op can link the point selected with a row of its dataframe to apply further processing.

This is not the case in Taipy where you only capture the position lat lon or the x y coordinate of the plot for a click event, and the index of the traces selected for the selected property.

Would it be possible for taipy to have this dash feature ? i.e. listen to the same property as dash, or simply get access to the custom_data of points clicked/selected?

A use case for that is the one I describe here :
"Just to be clear, my end goal is to be able to click on a point on the map, and get the index of the element of dataframe corresponding to the point I clicked."

Related to issue #1786

Acceptance Criteria

  • Ensure new code is unit tested, and check code coverage is at least 90%.
  • Create related issue in taipy-doc for documentation and Release Notes.
  • Check if a new demo could be provided based on this, or if legacy demos could be benefit from it.
  • Ensure any change is well documented.

Code of Conduct

  • I have checked the existing issues.
  • I am willing to work on this issue (optional)
@live2awesome
Copy link

kindly assign me the issue @ShootingStarD . i would like to contribute

@ShootingStarD
Copy link
Author

ShootingStarD commented Oct 15, 2024

kindly assign me the issue @ShootingStarD . i would like to contribute

I am not part of the Taipy team so I cannot assign it to you, moreover since it supposes major changes in taipy callback return structures, it has to be first discussed with Taipy maintainers

@FlorianJacta
Copy link
Member

@ShootingStarD I like this issue and how detailed it is. Thank you! We'll discuss it

@FlorianJacta FlorianJacta added 🖰 GUI Related to GUI 🟨 Priority: Medium Not blocking but should be addressed labels Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🖰 GUI Related to GUI ✨New feature 🟨 Priority: Medium Not blocking but should be addressed
Projects
None yet
Development

No branches or pull requests

3 participants