Already answered[^]

I copied your code as it is in to a new WPF Project and I had no problems at all i.e. the columns were visible in designer. I use VS2008(SP1).

I have a different opinion though. I feel separating it into a different section would make it easier to follow. It would demarcate the properties and bindings into separate group instead of all of them being together. It looks neat with just two entries but I would go crazy when the properties/bindings set through XAML would increase and make the node look ugly. This method has the obvious advantages of inherent implementation and access to all Mouse gestures in addition to the left and right click. But hey, as you feel comfortable. Cheers :)

If the user is behind a proxy then REMOTE_ADDR will be the proxy IP address and HTTP_X_FORWARDED_FOR will be the client IP address. HTTP_X_FORWARDED_FOR can consist of multiple comma separated IP addresses for each proxy the request passes through. Generally, client IP is the first of them. Finally, you can rely on the above methods only for Transparent proxies. There is no way to trace the actual IP in case of Anonymous or Distorting proxies. One more good tool for finding country from an IP is this one[^] on codeplex.

You can do it with a MouseBinding. Did you see my suggestion[^] ?

You can add a MouseBinding(or MouseGesture). Something like this,

<MouseBinding Gesture="LeftClick"
Command="ApplicationCommands.Open" />

MouseBinding needs the Mouse action and the routed command to be executed. You will have to add another MouseBinding for Right-click and also change the Command value to the routed command to be executed in your case. For more details, see here[^], here[^] and here[^]

Code-behind would be something like this,

yourControl.SetValue(Grid.RowProperty,1);//first row
yourControl.SetValue(Grid.ColumnProperty, 1);//first column

Try something like this,

<Menu DockPanel.Dock="Top">
<MenuItem Header="_File">
<MenuItem Header="Exit" InputGestureText="Ctrl+X">
</MenuItem>
</MenuItem>
</Menu>

And look at this[^] and this[^] for the CommandBinding option

This is my best attempt.

public class LogMessage
{
public string Message_Name { get; set; }
public DateTime LogTime { get; set; }
}

Then you have your list of messages like this,

List<LogMessage> messages = new List<LogMessage>();
messages.Add(new LogMessage(){Message_Name = "Dummy Message", LogTime = DateTime.Now});

lstViewLogWindow.DataContext = messages;

You have misunderstood what I said. Assign the LIST of MESSAGE to the DataContext. e.g.,

lstViewLogWindow.DataContext = yourListOfMessages;

where yourListOfMessagesis something like 'List<YourMessageType>' and YourMessageTypeis a type having Message_Name and DateTime property

By adding the item explicitly you are overriding the binding mechanism. You should do it by binding. Assign ListView's DataContext with the list of messages.Something like this,

lstViewLogWindow.DataContext = yourListOfMessages;

But you have not bound any property of the collection to the ListBox item. How do you expect the collection to change?

You should try something like this Link[^]

It won't work because you are binding the TextBox to the ContentPresenter. There is no binding to your data element at all.

You code did not come through.

Ok. So, data is displaying correctly just the updates you make to PhotoMetadataList are not getting propogated to PhotoInformationWindow ? Updates(CollectionChanged/PropertyChange?) are done in PhotoInformationWindow itself or in the Parent Window ? Well, any DataBinding errors in the Output window ? If my questions seem relevant then, How about setting PhotoMetadataList as the DataContext of PhotoInformationWindow instead of accessing it as a _StaticResource_ ? After setting it as the DataContext of PhotoInformationWindow bind ListView's ItemsSource using RelativeSource binding. I would certainly try attempting this with a WPF ListView (if its a similar model) before making frustrating attempts with the third party control vendor.

Look here[^]

If it answer's your question - Style Triggers[^] ?

Take a look here Karl,Josh[^] and here MSDN[^]

SR81 wrote:

It could be because the combobox contains nearlly 500 rows?

That doesn't seem logical. Perhaps because changes to VisualTree will be making it difficult to decide what to use as SelectedValuePath. Just a guess.