Releases · quantopian/qgrid
v1.3.1 🌈 v1.3.0 🌈 What’s Changeddf
attribute or any other attributes were changed. This issue has existed since 1.0. (#186)$('.q-grid').data('slickgrid')
as suggested here: #178 (comment). This allows you to work with a particular SlickGrid instance from the js console.show_grid
method. Options can be provided for all columns via the column_options
parameter, and for individual columns via the column_definitions
parameter.edit_cell
, change_selection
, toggle_editable
methods for updating the state of an existing grid widget without having to call show_grid
.add_row
method so that the caller can specify the values for the new row via the row
parameter. This will allow people to add rows to a qgrid instance even if it's showing a DataFrame that doesn't have an integer index.remove_row
method so that the indices of the rows to remove can optionally be provided via the rows
parameter.on
and off
methods at both the module-level (for listening to events on all qgrid instances) and at the instance-level (for listening to events on individual qgrid instances)on
and off
methods mentioned above should now be used to listen for events instead of listening for the on_value_change
event of the _df
attribute. In other words using qgrid_widget.observe(on_value_change, names=['_df'])
for being notified about changes to the state of the grid (i.e. editing, sorting, filtering) will no longer work.Merge pull request #194 from quantopian/events-api Events API
You can’t perform that action at this time.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4