"Input directory" and "Output directory" can't be loaded

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Start up the gdx-texturepacker-3.2.0 by following command:
java -jar E:\git\libgdx\release\gdx-texturepacker-3.2.0\gdx-textu
repacker.jar

2.Open a project file which i saved before.
See the attach file.

3.The "Input directory" and "Output directory" can't be loaded.
See the attach file. 

What is the expected output? What do you see instead?
The "Input directory" and "Output directory" can be loaded.

What version of the product are you using? On what operating system?
Product Version: 3.2.0
Operating System: 64bit Windows 7 Ultimate

Please provide any additional information below.
Java Versoin:
    java version "1.7.0_04-ea"
    Java(TM) SE Runtime Environment (build 1.7.0_04-ea-b16)
    Java HotSpot(TM) 64-Bit Server VM (build 23.0-b17, mixed mode)

Original issue reported on code.google.com by seker2...@gmail.com on 13 Oct 2012 at 10:09

Attachments:

• 1.png
• project

[GoogleCodeExporter]

This stumped me for a while until i started looking at what the saved project 
paths were.
The gui packer needs to be on the same drive as the texture you're trying to 
open. If there is a drive letter in the path it will not fill the input or 
output directories.

Steps

1. Copy the packer to the same drive where your images are stored.
2. Open and create a new project with a new pack.
3. Save the project on the same drive as your images and the texture packer.
4. Close packer, reopen, all folders are filled out.

Original comment by sdgus...@gmail.com on 7 Feb 2014 at 2:29

[GoogleCodeExporter]

On Linux there is an issue with such folders:

Input: /media/apofis/praca/android/casual/brickenoid/topack/game
Output: /media/apofis/praca/android/casual/brickenoid/topack/

The output won't load most of the time in such configuration.

Original comment by magne...@gmail.com on 11 Feb 2014 at 11:36

[GoogleCodeExporter]

I have had a similar issue where if you try an "open" a 2nd project file the 
input and output paths are not updated and still show the previous project 
file's paths.  By selecting another pack (if your project has multiple packs) 
it will suddenly cause the input and output paths to be updated.

Original comment by RyanLind...@gmail.com on 7 Aug 2014 at 1:41

[GoogleCodeExporter]

In the MainWindow.java file at approximately line 199 there is the following if 
statement:
if(packs.isEmpty())
    packsList.clearSelection();
else
    packsList.setSelectedIndex(0);

These lines should be changed to the following:
packsList.clearSelection();
if(!packs.isEmpty())
    packsList.setSelectedIndex(0);

The above change will cause the valueChanged method to be called again thereby 
causing the input and output directories to be refreshed.  The cause of the bug 
is when index 0 was already selected by a previous project file and the new 
project file tries to select index 0 again and valueChanged doesn't get called 
again.  By clearing the selection and re-selecting the index it forces 
valueChanged to be called again.

Original comment by RyanLind...@gmail.com on 7 Aug 2014 at 3:33