1:I don’t know of there is a special reason I’m missing this is how it is, but it I make an item invisible with…
2: I thought there used to be an option to turn this off, but since there is also snapping (I think that’s how it’s called) to the edges of items when you are moving an item in edit mode and not only to the center of another item I can’t find it anymore. I actually like the item snapping, but the thing that I would really like an option for or to be turned off by default is that the snapping also works with invisible items. I use quite a lot invisible items in a small space and it gets a bit annoying seeing all the bounding boxes because now the items is just snapping from place to place.
I might be asking for things that not a lot of people would use, but if you can find the time I would really like to see them implemented :).
Thanks for a great launcher
Colin
]]>
D5 Creation
< ![CDATA[
Turn snapping on or off with the icon between the geometry editor button and the pin button.
It looks like a dot with lines radiating from it.
Not sure if that’s what you’re asking…
]]>
< ![CDATA[
Ah found it! Thanks! 🙂
]]>
< ![CDATA[
Regarding item visibility, I don’t plan to make it persistent. What you can do instead is to set a 0 alpha, it should work the same but will be saved.
]]>
< ![CDATA[
But with 0 alfa it would still be clickable right? It’s not really a big problem though. I already have a way in mind to make the items that need to be invisible invisible on start.
]]>
< ![CDATA[
Yes that’s right. I guess you need to use the resume event and set some items invisible…
]]>
< ![CDATA[
Yep, that’s what I was thinking of. The only problem is I already have something running on the resume event, so I’ll have to come up with a nifty way to run both actions
]]>
< ![CDATA[
Maybe call each of your scripts in another top level script this way:
LL.runScript(“foo’);
LL.runScript(“bar’);
]]>
< ![CDATA[
Yeah something like that. I might not yet need it, but I would like a function or even seperate script that is able to handle all the different eventhandlers and you could add as many eventhandlers on the same event as you want. Kind of an eventbus to subscribe to if you know what I mean
]]>