Hi,
I'm new to the NetAdvantage controls. I'm using UltraDayView control to show appointments with the Office2007 view style (UltraCalendarLook control used by UltraDayView has property ViewStyle set to Office2007). My problem is that with this style only Subject and Location are shown in appointments, but i can't find setting to show also Description (and Time) as are in default view style. Can somebody tell me if this is possible and how. Thanks.
There is no way to make the Description appear using the public object model.
One way to solve the problem is to use the IUIElementCreationFilter interface. There is a Knowledge base article which demonstrates how:http://devcenter.infragistics.com/Support/KnowledgeBaseArticle.aspx?ArticleID=7316
Since the article was written before the Office2007 ViewStyle was introduced, the AfterCreateChildElements method must be modified in the following manner:public void AfterCreateChildElements(Infragistics.Win.UIElement parent){ // If the parent is an EmbeddableUIElementBase, get the associated AppointmentUIElement // and remove all elements except for the EmbeddableUIElementBase, and change the bounds // of the EmbeddableUIElementBase to occupy the entire bounds of the AppointmentUIElement. EmbeddableUIElementBase embeddableElement = parent as EmbeddableUIElementBase; AppointmentUIElement appointmentElement = embeddableElement != null ? embeddableElement.GetAncestor( typeof(AppointmentUIElement) ) as AppointmentUIElement : null;if ( appointmentElement != null ) { // Get the associated appointment, and the text that should be displayed for it. Appointment appointment = appointmentElement.GetContext( typeof(Appointment) ) as Appointment; string text = this.GetAppointmentText( appointment );
// Set the bounds of the embeddable element embeddableElement.Rect = appointmentElement.RectInsideBorders;
// Get the embeddable element's TextUIElement TextUIElement textElement = embeddableElement.GetDescendant( typeof(TextUIElement) ) as TextUIElement; if ( textElement != null ) { // Change the text displayed by the embeddable element based on // the DisplayStyle. textElement.Text = text;
// Reverse iterate the AppointmentUIElement's ChildElements collection // and remove all elements except for the EmbeddableUIElementBase UIElementsCollection childElements = appointmentElement.ChildElements; int childElementCount = childElements.Count;
for ( int i = childElementCount - 1; i >= 0; i -- ) { UIElement element = childElements[i]; if ( element == embeddableElement ) continue;
childElements.Remove( element ); } } }}
We recently changed our software to allow the Office2007 ViewStyle and thus just found this issue where the Description will not appear for the Appointment on the UltraDayView. While I can appreciate the workaround(s) published with this post, I'm wondering if anything more straightforward has been implemented in the software in the last 4 years. We recently upgraded all our Infragistics controls to the latest 12.1 version.
Thanks
This is the entity framework site I was referrng to http://data.uservoice.com/forums/72025-ado-net-entity-framework-ef-feature-suggestions
Hello,
I will refer this matter to the experts who are in charge of these requests.
Have you seen what the entity framework team did for this sort of thing? They created a site where users could vote on the things they thought were most important. Any user could create a feature request, and each registered user had, I think, ten points they could use to vote on features that they felt were worth including. I think there was a limit on three things each user could allocate points to at any given time. It worked really well
Hello peelports,
We have an internal system which calculates the importance of every request, based on the number of users which want this idea to be implemented, based on the control, etc.
Is there anywhere that we as users can look at items such as these and indicate that they are important to us as well? It doesn't seem like an awful lot has been happening in the winforms tools for the last few releases, and it seems like adding flexibility such as this to existing controls, whilst being less of a headline grabber, would benefit more users than some of what additions there have been?