Piping Failure mechanism can only be added if no piping failure mechanism is assigned to the wti project. Calling remove on presenters which…
Show more
Piping Failure mechanism can only be added if no piping failure mechanism is assigned to the wti project. Calling remove on presenters which do not support it will now throw InvalidOperation exceptions. Moved Initialize and Clear logic of PipingFailureMechanism on WtiProject to WtiProject. Related to Issue [WTI-13]git-svn-id: https://repos.deltares.nl/repos/WettelijkToetsInstrumentarium/trunk@272 5a3db67b-de53-47b5-99c8-a1c30a6650e2Former-commit-id: 3dc0ae91b502f02eaa4fc368991ad8ef7d7e5a9c
Show less
1691
+ 80 more
- 1715
- 1722
- 1792
- 1832
- 1833
- 1840
- 1842
- 1912
- 2199
- 2511
- AssemblyExport
- CSharpWrapper
- CloseOutputViews
- FailurePathsInvestigation
- LocationsFile
- MapSelection
- MapSelection_2
- Multiple_HRD
- Multiple_HRD_2
- Multiple_HRD_3
- Multiple_HRD_4
- Multiple_HRD_5
- Multiple_HRD_6
- Multiple_HRD_Final
- Multiple_HRD_Storage
- PipingProbabilistic
- Release16_1_1
- Release16_2
- Release16_3
- Release16_4
- Release17_1
- Release17_2
- Release17_2_Development
- Release17_3
- Release17_X
- Release18_1
- Release18_1_Development
- Release19_1
- Release21_1
- Release22_1
- Release23_1
- Release24_1
- Rename
- ResultsOverview
- Signing
- TargetProbabilityDependentHydraulicBoundaryLocationCalculationsInvestigate
- apitryout
- feature/1210
- feature/1552
- feature/1605
- feature/1860
- feature/1887
- feature/2002
- feature/2394
- feature/2449
- feature/2453
- feature/2511
- feature/2583
- feature/2588
- feature/2594
- feature/2652
- feature/977
- feature/OI
- feature/netStandard
- feature/preprocClosure
- feature/preprocessor
- feature/readGml
- master
- remote-run/DPCTest
- remote-run/EF_upgrade
- remote-run/EntityFrameWork
- remote-run/FluentRibbon
- remote-run/Multiple_HRD_Final
- remote-run/NETUpgrade
- remote-run/NUnit
- remote-run/buildServer
- remote-run/mapTimer
- remote-run/package_upgrade
- remote-run/storage
- signed
![]() |