I am currently using the Ag-grid enterprise angular version 20.2.0 in a project and we cannot find an option to deselect already selected cells during the range selection. In addition to that, I cannot find any information about that option in the given doc. https://www.ag-grid.com/javascript-grid-range-selection/.
Is there any possibility to deselect cells with ctrl and another key or do I have to create a feature request, so that they may implement that?
Just as further information, we use the api.getRangeSelections() to process and visualize the given values in a custom status bar component. We expect that customers demand to exclude unexpected data instead of deselecting everything and restart from scratch.
Thank you in advance for your assistance :)
Very good question. After a quick research on the doc, I can recommend you to enable advance range selection, and prompt users that they can exclude their selection only if they go around the cells they want not to select.
For example:
Here above, I selected cells with 'advance range select' ( CTRL + selection ) and remained a cell none-selected. Before I start to select with range, I figure it out which one I am not going to select, so it becomes easier to manage cells to be none-selected.
Go and experience yourself with this link: https://www.ag-grid.com/javascript-grid/range-selection/#example-range-selection-advanced
Related
I need help! I also reported this on grafana community. I hope someone has this experience with me here.
I have a table with couple of rows (per day) with LCD gauge cell display mode each columns. As the Dates grows, it will pile up and they will scroll up/down to it. (Refer to screenshot below)
Would it be possible to group it by 7 or 10 per page/view or depending on the value set? And just have the Next/Previous button for other page, and at the same time still has cell display mode applied?
Im looking at the DataTable Panel, but it doesn’t support the cell display mode (like LCD gauge).
Looking forward for some of your answers. Thanks!
Thanks for confirming the version; so paginations i.e. setting up rows per page was definitely an option in pre v7 table panel but it seems they have dropped the support in v7.
check this link pls -
https://community.grafana.com/t/pagination-in-table-grafana-7-0/31170
I have a large tableau dashboard including a number of charts and Summary views and attached to these I have a number of multiple value text filters all non calculated fields.
I am trying to improve the update speed and wonder if there is a method of setting these specific filters so that the views update after the full selection is made and the user has toggled off the filter option. Currently the views update each time a option is selected from the tickbox list.
Does anyone know a method of doing this?
Thanks in advance.
Dan
Simply click the drop down arrow on the filter menu > go to “customize”, then click “show apply button”.
Abhishek Boorugu answer should work for you Dan. If you want data to be filtered before the dashboard is loaded, try Context Filters. More explanation on the same can be found here
Is there a way to add a custom column menu tab with my own favourite icon which on click would render my custom react component?
something like
myColDef.menuTabs: ['generalMenuTab', 'filterMenuTab', 'myCustomMenuTab']
FYI I'm using v12.0.2
What you're after can't be done I'm afraid. The grid supports React components in all sorts of ways (renderers, editors, filters etc), but not via the column menu.
I've updated the docs page to remove the gibberish issue - it'll be fixed properly in the next release, thanks for highlighting this.
This would be helpful to have. In particular for us, we'd like to filter based off row properties, and not row values. Creating our own tab to filter by cell colors that we have assigned with our own set of labels would be useful.
I agree that it would be a nice feature to have. Apparently, there's no quick out-of-the-box solution to do it. The only workaround I see is to implement your own custom Header component which would display any buttons your want.
There you can put a button to open your own custom menu, which you can implement as any regular UI component. It also means you'll need to manually implement all standard menu options that Ag-Grid provides out of the box if you need them.
I have a set of tabs inside the window items layout in the database file.
when I click the plus popover button, I want it to generate a new record in the products layout and fill out all the fields based on the active tabs and the extra description field based on the last edit box field at the bottom of the tabs. can someone help me do this as I have tried a few different scripts and have had no success. once the record has been created in the products layout/table, I also want it to generate a record in the window item table based on the linked itemid field and the autoenter calculation that is setup on the description field.
this is probably all very confusing but I would be glad of any help you can offer.
Window Item Database Copy
Your question is more a problem than a question.
I'm assuming your questions:
1) should I use a script trigger for that?
Probably not. You should use a button to call the script, it should create all the records you need, come back to the layout and open the popover.
2) how to check the active tabs?
You should you the getLayoutObjectAttribute ( , "isFrontPanel" ). That will allow you to correctly set the ifs.
3) how to create a record in any table?
to be honest, you should start by going to the layout you want and then creating the record. That's an easier way.
What you are trying to accomplish is not that hard. You just need to break it in smaller steps.
I have a data entry form. Its properly tab indexed etc. and there are three dropdown menus which automatically unfurl with the on enter event.
No matter how much advice i give to users about using the tab key and keboard and checking what they just input.
they still insist on using the mouse to select values from the dropdown menus
the problem is that in their haste they often make mistakes as a result of using the mouse.
I would like to be able to force users to input into these fields using the keyboard.
the drop down is neccessary for users see the appropriate values for the field because the values will vary based on previous selections.
I have already tried experimenting with onclick events but to no avail.
Is there a way I can do this?
i am using access 2007 many of the users have access 2003.
Based on your comments, I would take one of two different approaches.
If your users are really comfortable with the codes AND know which ones they should use based on their previous selections, then just use text boxes instead of combo boxes. You can still put some validation code in either the Form_BeforeUpdate event or the individual control's _BeforeUpdate event.
If the users are not that comfortable, then I would suggest you have the first field in the combo boxes be the description of the code, not the code itself. So instead of choosing from 101, 102, 103 they are instead choosing from "Small", "Medium", "Large" or whatever those codes actually apply to. If you still wanted to display the codes themselves, you could do that with a separate disabled text box.
Now to answer your actual question. For the record, I highly recommend against using this approach. The simplest way I can thing of to prevent your users from using the mouse to select the combo box, would be to add a Transparent button covering the combo box.
To do this, draw a regular command button over the combo. Set Transparent = Yes, Visible = Yes, Enabled = Yes, Tab Stop = No.
When users click on the combo now, they will actually be clicking on the Transparent button and nothing will happen. The ONLY way they will be able to get into the control is by tabbing from a neighboring control or using a hotkey (via '&' in attached label).
Once they enter the control via Tab and your code forces a dropdown, they will still be able to choose an option using the mouse. But by forcing them to use the keyboard initially, it will make it much more likely that they just stick with the keyboard.
Again--I can't stress this enough--I think this is a terrible, horrible, no-good idea. Please don't use this approach. But you asked a technical question and this site is all about giving technical answers, so there you go...