Bug in item ordering?

[Maelstorm]

I think that I may have identified a bug. Consider the following code:

selected.0.0=1
description.0.0=Baseball
helptext.0.0=This will install the Baseball mouse cursor scheme.
command.0.0=CMD.EXE /C %SCRIPTSDIR%\SYSTEM-MAININDEX.CMD %BASEDIR% 

selected.0.1=1
description.0.1=Basketball
helptext.0.1=This will install the Basketball mouse cursor scheme.
command.0.1=CMD.EXE /C %SCRIPTSDIR%\SYSTEM-MAININDEX.CMD %BASEDIR% 

selected.0.2=1
description.0.2=Billards
helptext.0.2=This will install the Billards mouse cursor scheme.
command.0.2=CMD.EXE /C %SCRIPTSDIR%\SYSTEM-MAININDEX.CMD %BASEDIR%

If I remove .0.1 and do not renumber, then when WIHU is ran, .0.2 doesn't show up in the list. This seems to be pretty consistent across the board as far as numbering is concerned.

[BenjaminKalytta]

No this isn't a bug since each number have to be continuous numbered. If you remove .0.1 you have to fill the gap between the next entry.

Recommended procedding:

Deleting item 1.1 from List

Before

Example:
1
    1.0
    1.1
    1.2
    1.3

After deleting

Example:
1
    1.0
    1.2
    1.3

After adjustment

Example:
1
    1.0
    1.2
    1.1

If I remove this restriction, it would mean that loading ini file would take very long (some seconds) because each level s recursively loaded.

Edited June 14, 2005 by BenjaminKalytta

[BenjaminKalytta]

Changes in Version *.2: /HasGaps switch may be used to support ini files with uncontinuous keyword indizes. But, note, this will slow down ini file loading process.

Benjamin Kalytta

[Maelstorm]

That helps. Thanks.