If you have a cell selected that is not in edit mode and you try to tab the default MS behavior is to not tab through the cells but to transfer control elsewhere.
I do not agree with this behavior. I can see some rational behind it but I find it more irritating than helpful.

Also by default the behavior will ignore columns which are marked as readonly and not let you tab to that column.
I find this particularly irritating as it precludes that if a column is readonly then it is of no interactive value to the UI. Sure you can click in the column but you just can’t tab. I feel this should be based on the IsTabStop property rather than the IsReadOnly property of the column.

I am “correcting” this behavior in my version and I am adding a check for the IsCellReadOnly property I added. Right now it ignores it which doesn’t really hurt anything but I want things to be consistent – at least what I define is consistent

I will revist this more in-depth.

Sure it wipes out whatever you typed once it loses focus but seriously, thats pure slacker BS! Yes you can also implement an attached behavior to stop the user from typing invalid characters but its still BS.

Oh and the control doesn’t give you a MaxLength property (you can add a maxlength to the textbox in a template if you want to write a new one for every time you use this control) so you can type all day if you want. Yes it has a Maximum value but it only enforces after it loses focus and by then your subjected to the fact that if you type a reeeaaaallly long number it crashes! So then you go back and handle the Parsing event and do you own magic to prevent the crash. So to make this ‘Released’ control function as a user would expect it to you have now written a behavior (or code somewhere) to prevent it from crashing and to keep users from typing in non-numeric data in a NumericUpDown.

Another quick one, there is a ValueChanging/ValueChanged event you can handle too. But it only fires when you use the up/down control/keys and not when you change the Value property.

I was having a problem that when the Expander was collapsed the grid containing the expander did not resize properly unless it was recycled. In my case this grid was inside a DataGrid. So those this code is specific to my use (of an expander inside a grid) it can be easily adapted to other types of containers…or you can just wrap your expander in a grid and use it like its posted!

Just add this to your Expander_Collapsed event and call it good.

New Features

1. IsRowReadOnly – added to DataGrid and is a bindable property that allows you to set individual rows into a readonly state! It most literally simply prevents the grid from putting a cell in that row into edit mode. So now if you have a property on your model that indicates that the entity is readonly you can bind it to IsRowReadOnly and it will be evaluated for each row.
2. IsCellReadOnly – added to DataGridColumn and will only take a binding expression. This expression is evaluated for each cell in that column. So if you have some property or business model logic that identifies a cell as readonly you can map that binding to this property and PRESTO, the cell is readonly
3. VerticalScrollIncrement – allows you to define a fixed vertical scroll increment. If this is left empty or set to 0 the datagrid will scroll as it always has.
4. Vertical MouseWheel Scroll – its a quick and dirty implementation and only works for vertical scrolling but its better then nothing
5. EnableOneClickEdit – if set to true then you can put cells into edit mode with one click, not one click to select the row and then one click to edit cell. A positive side effect is that checkbox columns now check and uncheck on click.

DataGrid

• There is no way to indicate a row should be readonly (I have a fix).
• There is no way to indicate a cell should be readonly (I have a fix).
• Scrolling is based on row height. Row height consists of row content plus row details, so if the details are “open” and they are tall enough to need to scroll to read it all…you cant! when you scroll it will completely shift it off the screen (I have a fix).
• I havent found a way to tab INTO a cell, tab through the controls in a cell, then tab OUT and to the next column.
• Control focus becomes screwy when a cell is in readonly mode.

TextBox

• No masked textbox! OMG
• No watermarked textbox

ComboBox

• No “standard” keyboard support (you know, press a key and go to that item in the list)

I have to find my list…there are more I promise!

Perhaps someone else can make use of it or extend it Get it here.

http://autoexpandover.codeplex.com

What does all that mean? Nothing really. My name is Robert and this shall be my blog and it shall be grand (refer to above statement regarding beginnings).