Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Novapoint Railway: Alignement Design: CRASHES on TRIM/EXSTEND commands #4

Closed
bcattoor opened this issue Mar 20, 2017 · 2 comments
Closed
Labels

Comments

@bcattoor
Copy link
Owner

bcattoor commented Mar 20, 2017

Context

When the user uses the build in AutoCAD commands TRIM/EXTEND, and hoovers the cursor in the proximity of an open alignement, fatal errors are common to occur. This leads to big frustrations with the users.

  • los of design data
  • multiple hours of work are lost by this bug

Information

Name Value
Software version NVP 20.05.FP2a
Software version AutoCAD 2017
Module name ea: RAILWAY
OS Windows 7
Reported by TUC rail (Hans / Olivier)
Vianova tracking number 749716

Expected Behaviour

No more crashes when using the TRIM or EXTEND commands in conjunction of an open alignement.

Actual Behaviour

Crashes occur on a regular basis.

image

Possible Fix/work around

FIX
As u can see in the screenshot, the software reports a LOCK VIOLATION, should not be that hard to find.

Workaround:

  • When using the TRIM/EXTEND command, close all open alignements.

Steps to Reproduce

  1. There is no consistent maner of reproducing this error. It occurs at random.

Context

Make sure to have an open alignement (or multiple), and use the TRIM/EXTEND functions on normal AutoCAD entity's.

@bcattoor bcattoor added the bug label Mar 20, 2017
@bcattoor bcattoor changed the title Novapoint Railway: Alignement Design: Novapoint Railway: Alignement Design: CRASHES on TRIM/EXSTEND commands Mar 20, 2017
@bcattoor
Copy link
Owner Author

An answer has been provided by Vianova Systems Benelux:

From Chris Dheere — Vianova Systems Benelux BVBA
Dit is een gekend probleem en doorgegeven aan ontwikkeling. Men gaat kijken of dit nog kan worden opgelost en geïntegreerd voor FP3.

Als ik hierover nieuws heb, laat ik iets weten.

Summary of response:

  • Problem acknowledged
  • Solution will be offered in feature pack 3
  • He will inform us when there is a solution is available

@bcattoor
Copy link
Owner Author

Should now be fixed within release NP20.0x FP4.

Gert Rombaut — Vianova Systems Benelux BVBA
23 Aug 2017
Dag Bjorn,

Dit ticket is opgelost in NP20.0x FP4!

Met vriendelijke groeten,
Gert Rombaut - Vianova Systems Benelux

TicketID: 749716

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant