We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Original report (archived issue) by myungkeun Lee (Bitbucket: myungkeun Lee).
A Model who has box geometry link does not spawned, when tag’s value in geometry has white space at the front.
Example
<?xml version="1.0" ?> <sdf version="1.4"> <model name='a_model'> <link name='box_shape_linnk'> <pose> 0 0 0 0 0 0 </pose> <collision name='col_box'> <geometry> <box> <size> 1 1 1 </size> </box> </geometry> </collision> <visual name='vis_box'> <geometry> <box> <size> 1 1 1 </size> <!-- size value has whitespace at the front--> </box> </geometry> </visual> </link> </model> </sdf>
Because before parse the value of tag, value string is splited to [“ “, size_x, size_y, size_z, “ “] when value string contain white space at front.
It occurs when parseSize function split ‘sizeStr’ with ‘\s+’regex.
So when trim() was added to remove the space, it was confirmed that the model with the box size containing front of white space could be spawned
--- var values = sizeStr.split(/\s+/); +++ var values = sizeStr.trim().split(/\s+/);
The text was updated successfully, but these errors were encountered:
Original comment by myungkeun Lee (Bitbucket: myungkeun Lee).
Sorry, something went wrong.
No branches or pull requests
Original report (archived issue) by myungkeun Lee (Bitbucket: myungkeun Lee).
A Model who has box geometry link does not spawned, when tag’s value in geometry has white space at the front.
Example
Because before parse the value of tag, value string is splited to [“ “, size_x, size_y, size_z, “ “] when value string contain white space at front.
It occurs when parseSize function split ‘sizeStr’ with ‘\s+’regex.
So when trim() was added to remove the space, it was confirmed that the model with the box size containing front of white space could be spawned
The text was updated successfully, but these errors were encountered: