StephenP

Thanks so much for using Grid FX. Could you send me the aspx markup for the grid? Also, check for the latest version. You can update through "Check for Updates" in the grid's smart tag wizard in visual studio or at http://support.softwarefx.com/ShowInteractive.aspx?Product=GridFX10&option=0. Let me know if you still experience the problem with the latest version.

Have you updated to the latest service pack? In the latest update we did lots of empty data fixes, which is what this looks like. You can update through "Check for Updates" in the grid's smart tag wizard in visual studio or at http://support.softwarefx.com/ShowInteractive.aspx?Product=GridFX10&option=0. Let me know if you still experience the problem with the latest version.

Hi, thanks so much for using Grid FX. We will work hard to ensure your experience is a great one. I could not reproduce your problem here. Could you send me the code you use for binding to the List?

Hi, Unfortunately that's an outstanding bug. The problem there is that since sorting is done via callback and not postback, the button's html is not updated. This will be fixed in our next service pack. If it's urgent I might be able to prepare a hotfix for you. Once it's fixed, all commands that affect the selected item, such as sorting, paging, and filtering, will use the postback. Additionally in the future we will provide a simple way for you to use callbacks and still update outside controls, such as the button in question. Also, you should set the selected item in the PreRender event as opposed to the Rendering event because the server-side viewstate for that item will not be saved and upon postback from some outside control (like that button), the item will no longer be marked as selected. Let me know how urgent it is. Thanks so much for using Grid FX!

1) Yes, Grid.Paging.TopPager.Style should have all the css properties you need. 2) Yes, this could be achieved by handling the Grid.PreRender event and putting "grid1.Items[0].Selected = true" in the method body. In the future we will expose a public property, such as Grid.Selection.AlwaysSelectAnItem. Would that be helpful?

I'm sorry, but that's not currenlty available. The selected row is held in the Grid client-side control, but it's an internal property and is obfuscated. So if I told you now, it would likely break later. We are working on releasing a full documented client-side API and I will contact you as soon as it's possible. Will that work?

Hi, The GridItemDeletingEventArgs has an Item property which points to the GridItem being deleted. e.Item.xxx If you do not see that, it's almost certainly because you don't have the latest version. You can get it from the Check for Updates smart tag in Visual Studio or from http://support.softwarefx.com/ShowInteractive.aspx?Product=GridFX10&option=0 The documentation should be updated as well. Our offices are closed right now so as soon as we open back up I'll get back to you on that. Thanks for using Grid FX! Let me know how it goes.

Hi, 1. Right now, no you cannot specify a css class(es) to apply to the border. Grid's border can be one of two main types: image based or css based. If you set Border.Type to one that ends in "Line", like SolidLine, we use css border properties. In that case, yes, I agree you should be able to use a custom css class. This is not possible today but will be in the near future. However, if you use one of the image-based borders, we cannot honor css classes as the image colors can't be taken from a css class; instead, you have to use property grid props to do it. Does that work for you? Also, have you checked out hte Grid.Palette property? It has like 40 different color schemes. If you haven't, I highly suggest it. The grid's Auto Format wizard is another fun way to play with the grid's aesthetics. 2. At the moment we don't offer multi selection. We shelved that feature before initial release, and will eventually build it into the product. Out of the box, grid only uses multi selection for deleting and copying more than one item. Were you planning to use multiple selection for something besides that? If so, please explain the scenario so we can get a better understanding of what you want and can ensure that the feature does what you need when we implement it. 3. Unfortunately, this feature has no disabling property. This will be included in the next service pack, in addition to other properties for customizing column resizing. Expect that soon. 4. Are you talking about scroll bars? If so, the only way to ensure no scrolling occurs is to not set Grid.Width or Grid.Height. Basically, if the content exceeds the size set in those properties, we have to scroll. I suppose we could not render scrollbars, but then the user would have no way to see the clipped content. Is resetting Grid.Width and Height enough for you? If not, what do you envision here? Thanks for choosing Grid FX. Your feeback was great. I am looking forward to your reply.

Hi, If you are getting the "no data in grid" message, most likely you don't have the latest version of Grid FX. We recently released a service pack that included, among other things, big improvements in the empty data area. Not only does the grid look much nicer when there is no data, we added a Grid.EmptyData property that has everythign you need to customize the look as well as the above message. Update is available at http://support.softwarefx.com/ShowInteractive.aspx?Product=GridFX10&option=0. Let me know how it works out. Thanks for using Grid FX!

Hi, thanks for using Grid FX. Your questions are great and I'm pretty psyched to answer them because 1-3 are addressed in an service pack we are finalizing right now. The good news is that to achieve 1-3 is very easy, because we added APIs for the modal form title, modal form runtime control, and error message. We are testing the heck out of the service pack at the moment, and if things go well, we'll release it this week. Rather than give you the detailed answers to your questions, I'd rather wait until there is a version out for you to actually use them on. So, I'll let you know as soon as we release, and I will include full answers. If for some reason we delay the service pack (which is very possible), I can build a "hotfix", which is basically a temporary version that you could use in the interim. Sound good? Regarding question 4, yes, that's where you should do your work if you are doing a 'manual' data update. Set Handled to true and you're good to go.