-
Hi, in my WPF app (csla3.8.x compiled under .NET4 and Bxf) I experience the following: An editable root object is edited and then saved (view stays open), then the user can trigger a status change to the object by clicking a 'Publish'-button. This invokes a DocumentPublisher-command that processes the object on the serverside, and returns an
-
Hi Jonny, thanks for the clarification. The equivalent code pattern can also be found in the code for ResourceGetter as well as in the Exists methods within ProjectGetter and ResourceGetter. Just search for "if (e.Error != null)" !
-
Hi Rocky, I found a code pattern in the CSLA samples (ProjectTracker.Library, V4-3-x) that does look "suspicious" to me. It is the following asynchronous factory method from ProjectTracker.Library.ProjectGetter: public static void GetExistingProject( int projectId, EventHandler < DataPortalResult < ProjectGetter >> callback) Inside
-
Reading your question again, I get the suspicion that you have not yet looked at the Project Tracker demo application, at least not as close as you should have! The hierarchical structure that you present typically comes from anticipations that we often have about the UI that we want to come up with in the end... Besides displaying the relationship
-
Found the solution myself... it has nothing to do with the "DisconnectedItem" thing nor the PropertyStatus control! It is a matter of providing a common DataContext for related controls the right way... I just had to set the DataContext on the container element: <GridViewColumn Header="OrderNumber" attprops:GridViewSort.PropertyName
-
This works: <UserControl.Resources> <bxfc:VisibilityConverter x:Key="VisibilityConverter" /> <DataTemplate x:Key="OrderInfo"> <StackPanel Orientation="Horizontal" DataContext="{Binding Path=Model}"> <TextBlock Text="{Binding Path=OrderDate}" Margin="3" Width="60"
-
Hi, I am developing a WPF application using VS2010 SP1 and a local version of csla 3.8.4 compiled under .NET4. In one of my views displaying a list, I just replaced a ListBox using an ItemTemplate with a ListView using a GridView as the View. Both the ListBox and the ListView have VirtualizingStackPanel.IsVirtualizing="True". I had no Problems
-
Thank you! But I already had changed that style with no luck. There must have been some stupid oversight from my side. I finally went back to the 3.8 implementation with just one little change: In PropertyStatus.cs, I replaced the method 'GetRealSource' with the version from CLSA 4. This version tests for ICollectionView. So far it seems to
-
I am using csla 3.8.4 compiled under .NET 4. In order to be able to use CollectionViewSource together with the PropertyStatus control in my WPF project as it is shown in the samples, I wanted to backport the PropertyStatus implementation into my version of 3.8.4. So far it compiles, but the error image does not show up when a rule is broken... It seems
-
OK, the issue comes up only for a default value of 0... But as that is the internal default for numeric types... it's a no-brainer then. Thanks!