A bug? A flaw? The Profiler won't load deeply nested profiles

    I've just noticed that RM did not load all the profiles from my PC (W7 64bit).
    It might be related to how long the absolute path was (certainly longer than 256 characters in some cases).


    Initially I just dragged the root folder onto RM. But I also noticed that if I went to a very nested folder, selected all the files and dragged them, RM imported just one of them (did not pay attention whether it was the first one).
    Notes:

    • this was not related to the other rigs being already present in the RM's DB;
    • dragging the profiles one by one always worked, regardless the folder's depth;
    • moving the root folder to a higher level in the HD fixed the issue.

    In general, I'm not sure about the cause or whether my analysis is correct: just a few assumptions from me. But wanted to point out this inconsistency nevertheless. HTH


    This is more a flaw than a bug. The Windows API has a limit of 259 path characters, and even the Explorer does not let you create longer paths directly. There are some ways of exceeding the limit, e.g. by renaming a folder that is in the beginning of the path, but most third party applications won't load those files then, even some Microsoft apps can't do it. I will have a look if we can support longer path names easily, but in general I'd recommend not to use paths that exceed the limit. Thanks for the report anyway.
    Arne

    Thanks Arne


    I created the path with Total Commander, a great German file manager, which allows managing paths of whatever length.


    Anyway, would this diagnosis be coherent with the fact that if I select a number of profiles and drag them, at least one profile is always added to the RM's db? why can RM read that single file is the path is too long?
    After all, I'm not sure the issue was the path's length.


    Thanks again