DmD 2.8.1 Shows Duplicate Stages in Project Browser

[Bolt]

Noticed this today for the first time, guessing it arrived when I updated to V2.8.  No big deal, FYI.

[franji1]

Noticed this today for the first time, guessing it arrived when I updated to V2.8.  No big deal, FYI.

Very strange.

Q1. What happens when you expand out both duplicate stages (e.g. ABBMainSG), what do you see?  What are the (duplicate?) Rung Numbers below the duplicate stages?

Q2. What happens when you double click on each of the 2 stages?  Where does the Ladder View go for "both" Stages?

Q3. What happens when you double click on the rungs below the two stages?  Where does the Ladder View go for "both" Rungs?

[Bolt]

Well, 30 mins later I was trying to commit some changes to the memory configuration, and DmD locked up (not writing to PLC, just the System Configuration panel.  After restarting the program, the stages also appear in single form again.  So, can't answer any of your questions in great detail, only that clicking on the first iteration one did get me to the stage I needed at the time.

[franji1]

If possible, could you email your project, or even better, all the backups (they are below the Project\Backup\AutoSave folder, look for a folder with the name of the project and include that entire folder and subfolders).

If so, please zip them all up and email them to support at hosteng.com.

[ATU]

By chance, were you copying ladder from another project when this happened?

[Bolt]

By chance, were you copying ladder from another project when this happened?

Nope.  Not real sure when it happened originally, but I was mostly making and editing new structures and replacing existing D, V, R, type registers with the new structure members.

[ATU]

It happened to me last year, but I was copying ladder out of another project. Once I restarted the program, it went away.

[franji1]

It happened to me last year, but I was copying ladder out of another project. Once I restarted the program, it went away.

If I remember correctly, the issue in 2.6 (and before) was that rung comment merging was not being doing done "atomically" from the Project Browser standpoint, meaning that after EACH rung comment, the Project Browser would COMPLETELY regenerate itself, iterating code-blocks and rungs, WHILE THE IMPORT MECHANISM was importing each rung comment.  We addressed that issue in 2.7.

HOWEVER, that doesn't mean there isn't a DIFFERENT ISSUE where the SYMPTOM is similar (e.g. duplicate stages/rungs).

It may not be project specific, but specific UI operation(s) during specific "windows" of "opportunity" to break it.