-
-
Notifications
You must be signed in to change notification settings - Fork 530
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
Implement Tabulator buttons #3111
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3111 +/- ##
==========================================
- Coverage 83.13% 83.09% -0.04%
==========================================
Files 192 192
Lines 25440 25460 +20
==========================================
+ Hits 21149 21156 +7
- Misses 4291 4304 +13
Continue to review full report at Codecov.
|
Wow. Some one thinks tables are important. I do too. Love it. |
I wondered about the use cases. I would say some very popular ones are "download file" and "open url". Are they easy to implement with these buttons @philippjfr ? |
I've just tried it and the event returns the row number, not the row index. Which means that to get a value one has to write something like |
That's what we do for selections and the expanded parameter as well, you should just be able to use |
I just find working with indexes usually more natural than working with row numbers but if this is what is already done elsewhere then let's favor being consistent. (This is concise enough anyway: |
Sounds like that iloc usage ought to be illustrated in the docs? |
is there a way to move button position to the left of the table? |
If you want to trigger custom actions by clicking on a table cell you may declare a set of
buttons
that are rendered in columns after all the data columns. To respond to button clicks you can register a callback using theon_button_click
method: