#26 closed defect (fixed)
Removing a key from its parent RegContainer value removes a zero char too much
Reported by: | Andreas Schnellbacher | Owned by: | Andreas Schnellbacher |
---|---|---|---|
Priority: | blocker | Milestone: | 2.0 beta |
Component: | NEPMDLIB | Version: | 1.18 |
Keywords: | Cc: |
Description (last modified by )
After executing
NepmdDeleteConfigTree \NEPMD\User\AutoRestore
the section RegKey is OK, but in RegContainer, the entry for \NEPMD\User
was changed from
AutoRestore.AutoSave.Backup.Colors. ... .Toolbar.
to
AutoSaveBackup.Colors. ... .Toolbar.
(zero chars replaced by single dots).
The faulty function is _removeKeyFromContainerList
of libreg.c
, which exists for a long time.
The removed RegKeys are:
\NEPMD\User\AutoRestore\Ring\LoadLast \NEPMD\User\AutoRestore\Ring\MaxFiles \NEPMD\User\AutoRestore\Ring\SaveLast
The removed RegContainer keys are:
\NEPMD\User\AutoRestore\Ring \NEPMD\User\AutoRestore
It may have relevance that two container levels were removed.
Luckily, this bug didn't appear until now. It has to be fixed before the deletion of a tree will be added to ImportUserTextConfig
, triggered by a DELETE:
value in user.cfg
.
Change History (3)
comment:1 by , 7 years ago
Owner: | set to |
---|---|
Status: | new → accepted |
comment:2 by , 7 years ago
Description: | modified (diff) |
---|
comment:3 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Note:
See TracTickets
for help on using tickets.
Fixed by r3011.
The bug occurred if 2 RegContainer levels were deleted. Then the upper level tried to delete that level again, which was already removed by processing of the upper level.