I'm using a WinGanttView with a configurable primary interval of days, weeks, and months. When viewing the timeline with a Months primary interval and if a task's start date falls in the middle of a month, the timeline bar displays as if the task started at the beginning of that particular month. Is this the expected behavior? If not, how can I configure it to display the exact bar length according to the duration, just how it is in MS Project. The same case is also observed when using Weeks primary interval.
We are using NetAdvantage for Windows Forms version 10.3
Please see screenshots below:
Primary Interval: Months
Notice that 2 tasks have only 62 days duration but their timeline bars are equal to the length of tasks with 92 days duration:
Primary Interval: Weeks
Notice that the timeline bars started on Sept. 26 even though the tasks' start date is still on Oct. 1.
Thanks!
Hello,
I will be happy to assist you with your question.After some research, I have sent your feature request directly to our product management team. Our product team chooses new feature requests for development based on popular feedback from our customer base. Infragistics continues to monitor application development for all of our products, so as trends appear in requested features, we can plan accordingly.We value your input, and our philosophy is to enhance our toolset based on customer feedback. If your feature is chosen for development, you will be notified at that time. Your reference number for this feature request is FR14177.
If anyone else would like this feature to be implemented in future iterations of NetAdvantage, please feel free to submit a feature request.Thank you for your request.
Hi,
I was wondering if there is a workaround for this? Thanks.
Hello clgroce,
Currently there is no particular workaround that I can think of for this behavior. I recommend submitting a feature request using the new webpage found my clicking here.
Please remember the following from my initial post:Our product team chooses new feature requests for development based on popular feedback from our customer base. Infragistics continues to monitor application development for all of our products, so as trends appear in requested features, we can plan accordingly.
Please let me know if you have additional questions regarding this matter.
This is the same issue that I have also been told has been added as a feature request. It has been bumped once from 2012 to April 2013. Clearly I am not the only person affected. I certainly hopes this new feature makes it into the first 2013 release, or indeed sooner would also be good.
I think this goes for all intervals.I have the same issue.When showing a task of 1 minute long, if the interval is set to to minutes, it will show the task as if it were 10 minutes long but it is actually 1 minute.This is a serious bug.
Hello Vincent Vial,
Please refer to the following forum post to find out when NetAdvantage 13.1 will be released:http://ko.infragistics.com/community/forums/t/77044.aspx
Please note, this feature is only available with NetAdvantage 2013 Volume 1 and its successors.
That's really good news.
When will it be released?
I can't see 13.1 in winform section on http://ko.infragistics.com/help/service-releases/.
Thanks
Hello All,
The following feature has been added to NetAdvantage 2013 Vol. 1:
When the TaskWorkingHourMode property is set to “AutoAdjust”, the GanttView automatically adjusts the end DateTime such that non-working hours/days are excluded from the Task's Duration calculation. Updated (13.1): For Timeline positioning feature, set the TaskPositioning property to “Proportional”. This allows for positioning the timeline and resizing the tasks proportional to the amount of time over which they span. Proportional means that the timeline span depends on the TaskDragIncrement value.
Please let me know if you have any questions regarding this matter.
We are also waiting for this fix...have been for many months now...have submitted an enhancement request but they keep bumping it. I sincerely hope they do it in 13.1 and properly, not some hoke work around fix
We are also waiting for this fix.
So will it be included in next 13.1 release?