I have a request from a client to create a new interface for some proprietary scheduling data we have in our SQL database.
The requirements are as follows:
The scheduling data needs to be laid out in a calendar format to be able to be viewed 1 day/week/2 week/month at a time and be able to switch between these views.Inside each day there needs to be detail and summary data. That detail and summary data can consist of multiple rows (tasks) and columns of data, all of which could have a custom format (text/back color) applied to them.They also want to see something like a progress bar as a background of each row that shows the percent completion of each task (row).
I was wondering if I could use an UltraMonthViewMulti or a UltraMonthViewSingle as the primary calendar control for this, possibly inject 2 wingrids to get the rows & columns (with formatting ability), but I am not sure if it would be the right way to go, or truly even how to accomplish this.
I appreciate any help or suggestions in this matter.
Seradex
Cool. Glad to hear it. :)
I just wanted to let you know that the information you provided was instrumental in achieving the desired goals. I managed to simulate the progress bar by manually drawing the back color for part of the appointment based on the percent complete of the task. I didn't require anything other than a static progress bar like indicator.
Loading an isl file is basically just another way of setting properties on the controls. Or, to be more precise, it's another way of resolving the values of those properties (since it doesn't actually set the property value in most cases).
So with a few rare exceptions, the isl doesn't let you do anything that the control doesn't already do. It's just a question of finding the right property to do it. :)
Thank you very much.
It appears that this was exactly the info was looking for. I wasn't planning to use an isl file in my application. I just couldn't figure out how to get it to do what I wanted.
Preventing it from loading the isl file and setting the ViewStyle to Office2007 appears to have done the trick.
Thank you very much for all of your help, it is most appreciated.
Hi,
Just to clarify... are you planning to use IG.Isl in your application? This is an Isl file that we use for our samples, but there's no reason why you need to use it in your application. You could use a different isl included with the Infragistics suite, create your own isl, or use no isl. Is there some reason why you are assuming that you will be using the same isl in your app that the sample is using?
If you are not going to use this Isl, then you might want to comment out this line of code in the sample:
Infragistics.Win.AppStyling.StyleManager.Load(islFile)
This way, the Isl is not loaded at all and you will see how the controls look without it.
At that point, you could either try to create an isl that gives you the look you want or try to get what you want via property settings in the application.
Anyway, regarding the 4 points you listed here, these all appear to be functions of the ViewStyle property. The ISL is setting the ViewStyle of the UltraDayView to Office2007. So you can either create an isl that does this or simply set the ViewStyle to Office2007 in code. The ViewStyle is a property on the UltraCalendarLook which is a component that all of the Schedule controls attach to, similar to the UltraCalendarInfo. So it will affect all of the controls.
It might be possible to achieve these settings individually (without setting the ViewStyle), but I'm not absolutely sure. Presumably, it would be done via some other properties on the UltraCalendarLook. I could check into it, if you need it.