Closed jwtx1980 closed 2 years ago
The png files are still missing, but the rest should be in there now. I'm unable to upload the icons right now, but they are any 16x16 png files that you want. There are also png files under Migradoc/Resources for the plan report that need to be uploaded. The target framework should be 4.5 for everything I think, but it should be in Nuget. Are you using PDFsharp-MigraDoc 1.50.4619?
On Fri, Mar 1, 2019 at 11:09 AM jwtx1980 notifications@github.com wrote:
First thanks for putting this together. It looks very interesting and I'm excited to see what all you've done.
Trying to get to where I can compile and run it, I've ran in to some trouble. I am relatively new to some of this so it maybe that I'm just making beginner type mistakes.
In any case, I started with a clone of the repository to a local directory using the Git GUI.
After that I worked through references, most of which I was able to resolve.
However, under plan check reporting - there is a reference for MigraDoc.RtfRendering. I have found what I think should go there on Nuget but, am failing to be able to install because of difference in target framework. V4.5 for the project, something different for the reference. Any clues here?
From there it seems like I'm missing,
Helpers: \PlanCheck.Script\Helpers\ContourHelper.cs \PlanCheck.Script\Helpers\DVHExtensions.cs \PlanCheck.Script\Helpers\HelixToolkitException.cs \PlanCheck.Script\Helpers\INotifyUserMessaged.cs \PlanCheck.Script\Helpers\UserMessagedEventArgs.cs \PlanCheck.Script\Helpers\UserMessager.cs
PNGs: \PlanCheck.Script\Resources\DoseInValid.png \PlanCheck.Script\Resources\DoseValid.png \PlanCheck.Script\Resources\PlanApproved.png \PlanCheck.Script\Resources\PlanRejected.png \PlanCheck.Script\Resources\PlanSum.png \PlanCheck.Script\Resources\PlanUnapproved.png \PlanCheck.Script\Resources\PlanVerification.png \PlanCheck.Script\Resources\TreatApproved.png
\PlanCheck.Reporting\packages.config
\PlanCheck.Runner\Properties\Resources.resx \PlanCheck.Runner\App.config
Any help/ info or guidance would be greatly appreciated. Again, I can see there was a lot of work here and am excited to see it operate.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LDClark/PlanCheck/issues/2, or mute the thread https://github.com/notifications/unsubscribe-auth/AMRRQhAQsRsXcFtx9hwwe2zBD5e4NtNNks5vSWzNgaJpZM4bZiw2 .
I was on the latest update of PDF-sharp-MigraDoc. Rolling back to the one you noted got the references worked out.
Currently the compiler is looking for two more files.
Plancheck.runner\Properties\Settings.Designer.cs Properties\Resources.resx
The complier is not asking for it yet but, I think I may be missing one of the Calculators, CollisionSummariesCalculator.cs? Properties\AssemblyInfo.cs
All of the files should be in there now. Let me know how it goes.
Thanks, Landon
P.S. I noticed that loaded PlanSums are broken in this version with constraint templates that have [%] constraints.
Thanks Landon! I'll give it a try in the morning. I'm familiar with the summation % problem. I have a code I'll share with you tomorrow that tries to address it. Its built on the dvh metric code as well but has some added features. Some could be useful. Thanks again!
Did you fix the % problem? I'm curious if there is a good way to address it.
Landon
I think I fixed the %dose constraint with plansums, at least for now. Let me know if anything else isn't working.
I made some changes to the repository. You still might have some problems but they should be fixable: 1.) Make sure the configuration manager has x64 for the Platform on all projects 2.) Right click solution, Manage Nuget Packages..., and restore the packages. You might also have to manually delete the migradoc references and nuget install PDFSharp-Migradoc to get them back.
I believe that could be added in PlanCheck.Reporting.MigraDoc/Internal/PQMsContent.cs.
You could do something similar to AlternateRowShading() method, but instead of row color, changing font color maybe? There could be an if statement on the goal/variation/not met and change it to the desired color.
Hello, I would like to make print for the Plan Check "PC" list how to do that, I tried to follow how you make the print for PQM but I failed to do that, so can you please tell me how the print pdf file get the data and then generate the pdf, I mean where to make changes to have PC also part of the generated report
First thanks for putting this together. It looks very interesting and I'm excited to see what all you've done.
Trying to get to where I can compile and run it, I've ran in to some trouble. I am relatively new to some of this so it maybe that I'm just making beginner type mistakes.
In any case, I started with a clone of the repository to a local directory using the Git GUI.
After that I worked through references, most of which I was able to resolve.
However, under plan check reporting - there is a reference for MigraDoc.RtfRendering. I have found what I think should go there on Nuget but, am failing to be able to install because of difference in target framework. V4.5 for the project, something different for the reference. Any clues here?
From there it seems like I'm missing,
Helpers: \PlanCheck.Script\Helpers\ContourHelper.cs \PlanCheck.Script\Helpers\DVHExtensions.cs \PlanCheck.Script\Helpers\HelixToolkitException.cs \PlanCheck.Script\Helpers\INotifyUserMessaged.cs \PlanCheck.Script\Helpers\UserMessagedEventArgs.cs \PlanCheck.Script\Helpers\UserMessager.cs
PNGs: \PlanCheck.Script\Resources\DoseInValid.png \PlanCheck.Script\Resources\DoseValid.png \PlanCheck.Script\Resources\PlanApproved.png \PlanCheck.Script\Resources\PlanRejected.png \PlanCheck.Script\Resources\PlanSum.png \PlanCheck.Script\Resources\PlanUnapproved.png \PlanCheck.Script\Resources\PlanVerification.png \PlanCheck.Script\Resources\TreatApproved.png
\PlanCheck.Reporting\packages.config
\PlanCheck.Runner\Properties\Resources.resx \PlanCheck.Runner\App.config
Any help/ info or guidance would be greatly appreciated. Again, I can see there was a lot of work here and am excited to see it operate.