Configurations treeview does not match menu structure for multi-level configs

[GoogleCodeExporter]

I am running Tunnelblick 3.2.8 (build 2891.3099) on OS X 10.7.5.

I use OpenVPN for several different projects and have a rather large list of 
configurations, including multiple ways to connect to several projects and 
sites.  Because of this, I organize my configs by service, site, and 
device/protocol.  If there is only one device, I omit that level.  Same with 
the site.

The dropdown menu I see is currently:

No Active Connections
-----------------
Connect Svc1
Connect Svc2
Svc3 >>
 +----Site1 >>
 |     +----Connect tun
 +----Site2 >>
       +----Connect iodine
       +----Connect tun
Svc4 >>
 +----Connect tun
 +----Connect tap
 +----Connect tun-tcp
Connect Svc5
-----------------
VPN Details...
-----------------
Quit Tunnelblick

That matches the directory structure under ~/Library/Application 
Support/Tunnelblick/Configurations where each configuration and its keys are in 
confname.tblk/Contents/Resources under the named configuration.

When I open the VPN Details dialog, under the configurations tab, the 
Configurations treeview structure doesn't sync with the dropdown menu.  I see 
instead:

Svc1
Svc2
Svc3
  Site1
    tun
    Site2
    iodine
    tun
Svc4
  tap
Svc4
  tun
Svc4
  tun-tcp
Svc5

Specfically, Svc3-Site2 is indented too far, and Svc4's devices are broken into 
separate nodes and not in the same order as listed in the dropdown menu.

Selecting a configuration works as expected, so this is purely aesthetic.

Original issue reported on code.google.com by petiep...@gmail.com on 21 Jan 2013 at 6:20

[GoogleCodeExporter]

Thanks for this report and for writing it so clearly. I can reproduce this 
problem in Tunnelblick 3.3beta32 also.

I plan do a complete rewrite of the code that presents configurations in the 
VPN Details… window. The rewrite will show the configurations in a way that 
is similar to the Finder's List View and will fix this bug.

Original comment by jkbull...@gmail.com on 21 Jan 2013 at 12:56

[GoogleCodeExporter]

Original comment by jkbull...@gmail.com on 21 Jan 2013 at 12:56

• Changed state: Accepted

[GoogleCodeExporter]

This issue has been fixed in r2199 and will be in the next beta release.

(The rewrite has not been done yet, though. Only this bug was fixed.)

Original comment by jkbull...@gmail.com on 19 Feb 2013 at 1:31

• Changed state: Fixed