Comments by Dan Neely (Top 18 by date)

Same here. I found it via intellisense while looking for IsSplitterFixed, figuring I'd just un/lock the splitter via the mouse events.

Apparently we're both blind. The FixedPanel property does exactly what I want. :doh:

I've ran into one problem with this. On the left side I have a tab control with datagridview's on each tab. If I resize the form the splitter is on to be smaller the datagridview on the displayed tab doesn't paint the area that was hidden before the Layout event increased the splitter distance again. This is happening both when the control is docked (fill) or anchored (4 sides) in the tab page.

It's also sub-optimal in that what I'm seeing is the form initially painting with the splitter bar moved and then repainting itself when the bar is restored to its old position.

And here I was thinking I was blind for not being able to find a property that had to be there...

Adding to this, if your resume is truthful about your having only basic knowledge of net (which is not unreasonable for an entry level slot), then any technical questions should be limited in scope and aimed at making sure you're not adding languages to your resume that you've never touched before.

Thanks Pete; at this point I'm going to have to step back and rethink a bit. Going more deeply into it seems like it might be more effort than I want to take at this point. Wetting my feet with WPF is a fairly low priority on what I'm working on, and I'm limited in how quickly I need to get it done, and I already know how to do at least 90% of the GUI in winforms.

A second question, is that setup locking me into a single file as the datasource? I hard coded one in for my initial testing but will need to be able to support switching between several once I'm finished.

When I put the xml there, the compiler pukes on me; it appears that d:IsDataSource="True" is only supported by Expression Blend which I don't have, and which is completely outside my budget for a personal project. I tried removing the offending attribute, at which point the compiler was happy and I could specify the binding source; but the generate/remove/edit property bound columns items in the visual studio properties panel all still error out with "you must set ItemSource before you can perform this action."

Is the 1st code snippet supposed to go into the .xaml file? If so, where do I need to place it so that it compiles?

*THWAPP*

If the path's valid perhaps the remote site is refusing to serve any data to searcharoo because it identifies as a bot.

Reason for my vote of 1
You're an idiot.

While 3GB is the most common result with a 32bit OS the exact amount depends on your hardware and drivers. If they're miserly in the amount of ram they reserve and only go for really high addresses you can get more than 3GB usable. If you have a gfx card (or worse two) with large amounts of ram you'll have less than 3GB free since every byte on the card needs mappped to a byte in the OSes 4GB address space.