Hi,
the ganttchart display deserialized data the wrong way. As you can see below task B & C are subtask of task A. The displayed data is the deserialized one. so before i serialized the data and saved to file i defined that task C is successor of task B. I should look like A1 and B1 are displayed. I hope it is no bug, that subtask aren´t properly handled. Has anyone an idea during my investigation, all my work stops at the unlove AllProperties member which contains the relevant propertievalues in a base64 encode string.... any idea? NA 10.2
Image shows the wrog behavior. task C should be after task B like the relation between A1 and B1.
It is difficult/impossible to analyze this with a screen shot. If you attach a sample that demonstrates the problem, we can take a look and let you know what is going on.
nothing easier than this
here the sample data:
don´t look at the code, its a quick sample... load the sample data change some thing, let C become successor of B click save... restart the app click load... the successor relation of the subtasks B and C is gone.
Thanks!
Hello Karsten ,
Thank you for your patience, while I had researching about yours issue. I discussed this behavior with our Development Team and my senior colleagues, and I couldn’t find a way to achieve your goal. So we decide to log this behavior with our developers in our tracking system, with an issue ID of 56870.
Thank you for your patience.
It cant be a problem with the ParentTaskId because this relation is ok. it must be inside your base64 encoded and encrypted AllProperties member because it seems to me that it handled there. However that be i changed the types aof the columns and made a cleaner sample.
i don´t get the point...
How to:
run the sample-> click 'init empty' -> add three tasks by contextmenu -> indent the last two tasks so they become child of the first one -> define task two as predecessor of taks three -> click 'AcceptChanges' (this is the method call of DataSet.AcceptChanges())
It would be realy kind of if you could provide a solution. Thanks!
Looking backward, it would be much easier there would be working sample instead of using my sample.
The ParentTaskId field needs to be able to support DbNull, which System.Guid does not. Since nullable types do not support DbNull either, you should probably just make the type object.