Nice! I was considering a mod like this with “B” as the align point, but forgot about it. I think I got sidetracked experimenting with another “face align” idea that never went anywhere.
And it’s implemented as a modal to!
The modded version 1D_Inc linked to is based off the 2017_09_29 version of NP Station for 2.78 / 2.79. It won’t run on 2.80.
You have an updated version of NP Station on github?! I wish I had known earlier, I would have merged those changes in to the “official” version in addons-contrib. That is where I have pushed all my NP Station updates to.
I agree, especially with the snap improvements Mano is working on that could require API changes.
I did do some experimenting with a 2.80 version of NP Station that would be based around the code changes I made for my Three Point Arch tool (with some of the API updates in the addons-contrib version of NP Station), but the code is not very far along.
I was referring to this, but on second glance this seems to be a more generalized version of point_move for external use.
I looked into a github version of NP Station, but I could not find a nice way to share commits between a github version and the one in addons-contrib (without mirroring ALL of addons-contrib). The only way to share commits seemed to be by manually copying commits from one version to the other. That would eat up a lot of time and could lead to a messy git history.
I still consider Okavango to be the main author and maintainer. I originally started as an assistant maintainer for NP Station. It’s just with Okavango having had almost no time to work on NP Station in the past several months, I have become something of a “de facto” maintainer.
This error looks interesting: object has no attribute 'user_preferences'
Which version of NP Station did you try to update from? The version of NP Station in addons_contrib that is included with the daily builds should have already had all instances of: user_preferences replaced with preferences
If you are trying to get NP Station running on 2.80, this version of NP Station from addons_contrib is what I would recommend starting from as it has already some 2.80 updates applied:
Getting the macro setup (the foo.define('bar') code in the register functions) running right can be rather troublesome though. This is one of the reasons why I have been experimenting with a rewrite of NP Station that would use modal operators instead of macros.
Here is the current work-in-progress version of “point move” without macros.
Note that this is an experimental version, so it is not recommended for use on any important or production level projects. This version is also missing some features and may work a little different than the “official” 2.7x version:
This version expects LEFTCLICK to be the “point place” hotkey, but I plan to make this configurable in a future release. This is a downside to using modals in 2.80, (IIRC) it is not possible to have add-ons use the hotkey settings in user preferences.
You can still change the add-on’s hotkeys by editing these lines in the “np_point_move_wip.py” file:
We should take a look at a way to expose such settings in addon prefs.
Will try to take a look as soon as possible.
In then meantime, great work done here (as usual), thank you NBurn !!
Yeah, a built in key editor would be ideal. There’s already at least one “default” add-on with this option, mano’s snap_line_utilities. IIRC, Smart Select (commercial add-on) can also do this. Re-implementing point_move’s snap feature took more time than I expected and I had something come up, so I had not had a chance to look into how those add-ons implemented their hotkey editors yet.
Hi
Thanks for releasing the original NP Tool and now for 2.8
I didn’t understand how this works in v.2.8.
After using it the wrong way a couple times, I figured it out BUT
Leaves rubbish “Mesh” named objects when not used properly and must somehow attach data to those and other objects. As it turned out, in the end no matter what object I picked and even after having purged the orphan mesh objects, the command would end up moving my active camera instead of the selected object!!
Has it corrupted some data? Is it the specifics of my file.
Edit:
It works in a simple small file.
When I load my current project it messes up. It starts moving cameras regardless of what object was selected when I initialize the edit, When it moves the camera it immediately changes it to an object called “Mesh”. After it’s done destroying my cameras… it starts with other objects.
Since it does not happen with every file I decided to upload the file.
Please note the file contains a couple of commercial material images that you are not allowed to copy or use. The file is uploaded only for testing purposes and I do not imply that the source materials can be copied or used. File is about 200MB
Edit: This large and complicated file is not needed. I have reproduced the bug in much simpler file, view the following post
Eek, I should have added a better disclaimer, but please do not use the “WIP” version for any serious or production level projects. It was intended only for experimental use, not as a replacement for the 2.79 version.
Yes, this was also an issue with the 2.7x version IIRC. I have not found a nice fix for this yet.
That is very strange, I have not seen anything like that before. The WIP version should only be moving objects that were selected before the tool was run. I tried the add-on with the blend file you uploaded and it is definitely doing something that was not intended, but I am not sure what is causing that bug.
If you have a file with assets you do not want to be made public, you can also send me a link in a private message.
Thank you. No other file is necessary since this reproduces the error , I think.
Note that it is not corruption of file data by your addon, since the error happens with previous versions of same file, before NP was run.
What is even stranger is Exact Edit’s Set Measure (which the “np_point_move_wip” release was partially based off of) does not have this issue.
The big difference is the 2.80 version of Exact Edit does not create and destroy mesh objects for snapping like point_move does, so the bug in the WIP version must have something to do with that.
Btw I like NP’s new interface more. I mean the gizmos in the viewport when it moves.
Not quite comfortable with whole other tab for every addon. I like incorporation in existing menus when logical.
I would kindly appeal to everyone to be as patient as they can. NP Station’s code is huge and it’s propper transition to 2.8 would have to be done after it’s optimisation and rationalisation in 2.7 versions, for which there is apparently no resources at the moment. There are numerous geometrical and graphical engines at play and they are all over the place.
nBurn has kindly offer to maintain the existing addon and has made some free time experiments to see what kind of effort the transition to 2.8 would require. No timeline, no promises and certainly no professional grade guarantees. The code was made by an architect and is a mess. Sit back, take a drink and watch stuff roll out at their own pace, as well as efforts by Balázs Szeleczki and Pablo Dobarro with their generation tools.
And it’s implemented as a modal to!
