Having the MC logic handy would help users describe bugs
Having the MC logic handy would help users describe bugs
I think if the users of MC had its underlying logic described in some detail on this forum somewhere for easy reference, it would help them describe the bugs better. I am also thinking that the order the studies are updated would be handy. I have this impression that it is the order in which the charts are intially created in the workspace. I could probably figure out the later part by using my database program and sending GV updates out to all the charts, getting the info back and checking for a consistent pattern. However on second thought the dumps create a log giving this information I would think. Is that not correct?