Bug #1147

Handlng of (Spaces in) target names

Added by Rob Baer almost 2 years ago. Updated almost 2 years ago.

Status:AcceptedStart date:03/12/2017
Priority:LowDue date:
Assignee:Joel Palmius% Done:

0%

Category:Code correctness
Target version:MakeHuman 1.1.2

Description

It seems target names with embedded spaces are not currently supported (at least on Windows) when a target position is saved into an .mhm file. The target shows up on the GUI and appears to function. It's position just doesn't make it round trip during a save.

Forum thread
http://www.makehumancommunity.org/forum/viewtopic.php?f=6&t=14079

History

#1 Updated by Joel Palmius almost 2 years ago

  • Category set to Code correctness
  • Status changed from New to Accepted
  • Assignee set to Joel Palmius
  • Target version set to MakeHuman 1.1.2

#2 Updated by jujube (Forum User) almost 2 years ago

After downloading blindsaypatten's targets from the forum, I replaced the spaces with underscores, but for some reason makehuman doesn't want to remember them! This is inconvenient, as I would really like to be able to use those targets.

Targets from this thread:
http://www.makehumancommunity.org/forum/viewtopic.php?f=3&t=14160&sid=086829e9716e581bc98b9edcd4937b90

#3 Updated by Jonas Hauquier almost 2 years ago

Spaces is not a good idea, they should be discouraged in filenames. But it should be able to handle underscores.
I'd have to check whether underscore has any special significance, which could by why it is not working properly.

Perhaps it should refuse filenames with spaces, so as to avoid any confusion.

#4 Updated by jujube (Forum User) almost 2 years ago

It turns out the problem was because I saved it in a subfolder, and the subfolder name had spaces in it.

#5 Updated by Jonas Hauquier almost 2 years ago

Not only that, but the subfolder name will also change the target names.
In any case they will always have to be in the same subfolder to be able to load them again.

Anyway, MakeHuman should probably refuse to load targets with spaces in the path (at least the part relative to the targets/ folder), or at least warn about this, or fix the problem.

Also available in: Atom