We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

Upgraded to v3 - Pressing TAB or ARROW moves to readonly/not Enabled Cols

Thread ID:

Created:

Updated:

Platform:

Replies:

23367 Jan 11,2005 06:58 AM Feb 6,2005 03:50 PM Windows Forms 6
loading
Tags: Grouping
Jason Hales
Asked On January 11, 2005 06:58 AM

Hello, Just upgraded to v3 of GroupingGrid and have this issue. We have a grouping grid with various readonly and non editable columns, and one or two editable columns If I click on, say, a checkbox col and press tab, the previous version would then jump to the next editable non readonly column. In this version it jumpts to next consequtive column - which is readonly and not editable. These are the styles we apply to readonly cols GridTableCellStyleInfo readOnlyStyle = new GridTableCellStyleInfo(); readOnlyStyle.CellType = STATIC_TYPE; readOnlyStyle.Trimming = System.Drawing.StringTrimming.EllipsisCharacter; readOnlyStyle.ReadOnly = true; readOnlyStyle.Enabled = false; and this our editable style: GridTableCellStyleInfo editableStyle = new GridTableCellStyleInfo(); editableStyle.ValidateValue.Minimum = minEditValue; editableStyle.ValidateValue.Maximum = maxEditValue; editableStyle.Trimming = System.Drawing.StringTrimming.EllipsisCharacter; editableStyle.ReadOnly = false; Have we missed something. One unrelated thing - I noticed that version 3 no longer automatically sets bool datatypes to CellType of CheckBox - we have to do that explicitly. But so far it all looks good and was pretty painless Jason

Administrator [Syncfusion]
Replied On January 11, 2005 08:04 AM

We have a private build that has this problem fixed. If you submit a Direct Trac support incident, we can give you a download link to try out this patch if you would like.

Jason Hales
Replied On January 11, 2005 08:29 AM

Thanks Clay. Any idea when this will fix will make it into a general release. We''ve previously had a few problems using private builds. Jason

Administrator [Syncfusion]
Replied On January 11, 2005 11:51 AM

We are trying to learn our lesson and not forecast when releases will be. That said, there should be a point release later this month. I do not currently know if this release will be a public release or not.

Administrator [Syncfusion]
Replied On January 12, 2005 05:24 AM

I totally understand ;-)

Richard Finch
Replied On February 4, 2005 10:00 AM

Does this bug also allow you to edit (delete key) the cells even though they are read only?

Administrator [Syncfusion]
Replied On February 6, 2005 03:50 PM

Richard, I tried to reproduce this. I added the following line in the GroupCustomers example: this.groupingGrid1.TableDescriptor.Columns["ContactName"].ReadOnly = true; After adding that line editing ContactName is not possible anymore, e.g. got to a record and move current cell to ContactName and press Delete. What''s the steps you used to reproduce the behavior you describe? Thanks, Stefan

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;