Search Results

Search found 7 results on 1 pages for 'vidalsasoon'.

Page 1/1 | 1 

• MVVM - Master/Detail scenario with Navigation and Blendability

  - by vidalsasoon

  Hi, I'll start off with what I want so it may be simpler to understand: I have a Page (Master.xaml) that has has a listbox of PersonViewModel. When the user selects a PersonViewModel from the listbox, I want to Navigate to a details (Details.xaml) page of the selected PersonViewModel. The details page does some extra heavy lifting that I only want done once the user navigates to the page. (I don't want too much stuff loaded in each PersonViewModel of the master listbox) So how do you guys handle master/detail scenarios with navigation while maintaining "blendability"? I've been turing in circles for the past week. there seems to be no clean solution for something that should be quite common?

  Read the article

• MVVM - RaisePropertyChanged turning code into a mess

  - by vidalsasoon

  New to MVVM so please excuse my ignorance. I THINK i'm using it right but I find my ViewModel has too many of these: RaisePropertyChanged("SomeProperty") Every time I set a property I have to raise that damned property changed. I miss the days where I could just go: public int SomeInteger { get; private set;} These days I have to stick the "RaisePropertyChanged" in everywhere or my UI does not reflect the changes :( Am I doing it wrong or are other people getting annoyed with the excessive number of magic strings and old school property setters? Should I be using dependency properties instead? (I doubt that would help the code bloat anyway) Despite these problems I still think MVVM is the way to go so I guess that's something.

  Read the article

• MVC noob - changing part of URL in a link

  - by vidalsasoon

  Hi, I have a site that supports localization. I would like to be able to switch between english and french. Let say the user is currently at URL: http://www.mysite.com/en/Home I would like to redirect to: http://www.mysite.com/fr/Home If the user click on a "French" link how to change the URL part to "fr" yet not change the "Home" part of the URL (basically I want preserve the current location of the user) Hope my question makes sense! I'm probably missing something very basic?

  Read the article

• Ria Services - Delay load images (or any heavy binary data)

  - by vidalsasoon

  I have an RIA Service that returns image data (Byte[]) and caption of image (String) from SQL Server. The data part can sometimes be a few MB's so it can take quite a while to load. I would like to load the bytes independently of the caption (which loads very fast). Is there a way to do this without having to create a second image context?

  Read the article

• Messenger -"Register" an instance and not a type with the MVVM Light Toolkit?

  - by vidalsasoon

  Hello i'm consfused using the Messenger class of MVVM Light. I have a ProductsViewModel that can get initialized a number of times. In the constructor of ProductsViewModel I have this code: Messenger.Default.Register(this, n = MessageBox.Show(n.Test)); The problem is, if I have 2 instances of ProductsViewModel, then Messenger gets registered twice. Is is bad to Register the Messenger in a constructor? Hope this makes sense!

  Read the article

• RelayCommands overriding the "IsEnabled" of my buttons.

  - by vidalsasoon

  RelayCommands overriding the "IsEnabled" of my buttons. Is this is a bug? Here is xaml from my View and code from my ViewModel <Button Grid.Column="0" Content="Clear" IsEnabled="False" cmd:ButtonBaseExtensions.Command="{Binding ClearCommand}" /> public RelayCommand ClearCommand { get { return new RelayCommand(() => MessageBox.Show("Clear Command")); } } Notice I hardcoded the IsEnabled="False" in my xaml. This value is completely ignored (button always enabled). I realize that RelayCommand have a CanExecute overload but I did want to use this as I want to do more than just have a disabled button.

  Read the article

• ObservableCollections in the ViewModel and IEnumerables in the Models?

  - by vidalsasoon

  Keep only ObservableCollections in the ViewModel and IEnumerables in the Model? Does following this general guideline make any sense? I'm thinking this is the way to go because the models don't care about updating the View with the RaiseNotifyChanged.

  Read the article

1