-
Notifications
You must be signed in to change notification settings - Fork 1
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
BABYlONJS #3
Comments
is there any command that can hide the TransformNode in this module? |
Hi @dheeju143, I haven't been using this node myself for a long time, but it seems from my code that I already have implemented something similar for lights in the past. So it should be possible to do something similar for meshes. I have quickly created an "enable-mesh" branch in this repository, that implements your feature (see here). I have very few time lately, so would be nice if you could test it and let me know whether it works.
|
@dheeju143, You can find an example flow on the readme page (see new Transform nodes section). When you create a mesh, you can specify the parent transform node in the input message: If you haven't created the transform node in advance, you will get obvious this error: Here you can see the result of the demo flow: Note that the transform node can currently only be applied as a parent to meshes. I thought that BabylonJs also supports it for some lights, but I have no time to read about that. So if you want it, it would be nice if you could look it up and summarize in this discussion where it can be used. As soon as you have tested this (and it works fine), I will merge it into the main branch afterwards... |
Ah damn, I had updated the readme page but seems I have forgotten to push my changes... You can also use an update_mesh message with a But I am not going to implement the entire BabylonJs interface. This ui node is made for the old Node-RED AngularJs dashboard is end of life for already quite some time. When I have free time, I will focus on migrating to Flexdash. That is the reason why I am not going to spend too much of my (very limited) free time anymore in these old ui nodes. But of course pull requests are always welcome. |
Thanks I will look into it |
@bartbutenaers I look into the 3D on which is sounds good!! i would like you ask more adding on features on below would be great. |
Do you mean that you have tested my changes, and it is working correctly so I can publish it on npm?
Do you mean something different compared to the current axes viewer possibilities?
I see here in my code that I have added at the time being a gui control for text. Which means for the command |
@bartbutenaers Yeah I will find out and let you know if I can have anything of annotations |
@bartbutenaers Yes the updated code is working fine you can publish it on npm |
@bartbutenaers any sample flow is there for GUI control for text block would be great! |
Thanks for testing! I had forgotten that this node is not available on npm, so I have simply merged the "enable-mesh" branch into the master branch. About the GUI control for text block. I saw this evening that there were some bugs and some required features were missing. So I have added them on a new "textblock-extension" branch. However it doesn't work for some reason. And unfortunately I don't have enough free time to digg further into this. The problem is that the linkWithMesh does not work: I link the textbox to a specified mesh, and then it should appear on top of that mesh (and also track the mesh if it moves). However it doesn't appear on top of the mesh. I don't know why... This was my test flow that I created tonight for this new branch:
|
ok Nice. meanwhile i will also check the Flow and test it. |
In the context of 3D layout design, there is a method available for the TransformNode class that allows you to hide all meshes contained within it. Specifically, you can use the "setEnabled" method to disable rendering of the TransformNode and all its child meshes. This effectively hides the meshes from view within the 3D layout.
The text was updated successfully, but these errors were encountered: