Hi I dont suppose you know if this fix has been released? any chance of a url to a release with this version in it. getting hold of JInput releases isnt very obvious

Cheers

shadow123

Thanks,

I rebuilt jinput with the change and tested it and it works fine.
when I posted the original code I forgot jinput is built for 1.4, so no templates and no annotations, so for completness the code change is.

      File[] files = dir.listFiles(filter);
      Arrays.sort(files, new Comparator(){
          public int compare(Object f1, Object f2)
          {
              return ((File)f1).getName().compareTo(((File)f2).getName());
          } });

and if anybody needs to fix the order of devices on a linux platform ie. writting rules this was a usefull link http://reactivated.net/writing_udev_rules.html

given that listFiles doesnt guarantee order, I assume this is due to LinuxEnvironmentPlugin listFilePrivileged doing


dir.listFiles(filter);


I dont surpose somebody who knows what they are doing could update the code to apply an alpha sort on it

File[] files = dir.listFiles(filter);
Arrays.sort(files, new Comparator<File>(){
    public int compare(File f1, File f2)
    {
        return f1.getName().compareTo(f2.getName());
    } });
return files;

I have exactly the same problem on a redhat platform. two devices same make and model (2 usb track balls).

I can not tell them apart at the JInput level as they both have the same Controller name, and each time you boot the machine its 50:50 the order Jinput returns them in the array of controllers.

using rules to force the device names in /dev/input I can force the names to be in the same order (based on the ID of the device) however Jinput doesnt seem to base the return of the controllers on the device name.

anybody know what it bases the order on, and can I get it consistant?