Skip to content
New issue

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

Find the external meshes in the local file system #798

Merged
merged 3 commits into from
Jan 11, 2021

Conversation

S-Dafarra
Copy link
Contributor

@S-Dafarra S-Dafarra commented Jan 8, 2021

CHANGELOG.md Outdated
@@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Added
- Add the possibility to plot and update frames in the Matlab visualizer.
- Added ``getFileLocationOnLocalFileSystem`` method in ``ExternalMesh`` that attempt to find the mesh location in the local file system
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we specify that this is now used when using the visualizer?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in a98f5ef

Comment on lines +258 to +262
if(isFileExisting(filename))
{
return filename;
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This ensure that the current use case of specifying files without a package:// URI file is still supported, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, if filename is already the path of a file, it simply returns it as it is.

@traversaro
Copy link
Member

cc @singhbal-baljinder this should permit to use the visualizer without any more specific hacks.

Copy link
Member

@traversaro traversaro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a small comment on the changelog. Thanks!

@traversaro
Copy link
Member

Related issue: #799 (that can be in any case addressed after this PR has been merged).

Fixed a few typos in the docs and in the changelog.
@S-Dafarra
Copy link
Contributor Author

Actually, there were a couple of bugs in the Windows branching. Indeed, I haven't tested it in WIndows 😅

@traversaro
Copy link
Member

So, did you tested on Windows now? Is this ready to be merged?

@S-Dafarra
Copy link
Contributor Author

So, did you tested on Windows now? Is this ready to be merged?

I haven't yet. I will

@S-Dafarra
Copy link
Contributor Author

So, did you tested on Windows now? Is this ready to be merged?

I just tested it in Windows too. It seems to be working (apart from the usual headaches when testing something on Windows)

image

@traversaro
Copy link
Member

Perfect, can you resolve the conflicts so that we can merge? Thanks!

@S-Dafarra
Copy link
Contributor Author

Actually, I forgot to mention that it did not work out of the box, simply because right now we don't define the GAZEBO_MODEL_PATH env variable (neither ROS_PACKAGE_PATH nor AMENT_PREFIX_PATH).

@traversaro
Copy link
Member

Actually, I forgot to mention that it did not work out of the box, simply because right now we don't define the GAZEBO_MODEL_PATH env variable (neither ROS_PACKAGE_PATH nor AMENT_PREFIX_PATH).

I opened an issue for this: robotology/robotology-superbuild#577 .

@traversaro traversaro merged commit 876e3b2 into robotology:devel Jan 11, 2021
@traversaro
Copy link
Member

By the way, how did you installed irrlicht on Windows? vcpkg?

@S-Dafarra
Copy link
Contributor Author

By the way, how did you installed irrlicht on Windows? vcpkg?

A bit worst than that, just a bit 😁 I downloaded the precompiled version from Sourceforge, I added the bin folder to the path and set the CMake variables (pointing to the include folder and the to the Irrlicht.lib library) manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants