More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided.

hi, could add this to contrib shortly, would need the pep8 clean up first

Added note in docs, closing.

This is working as intended, select multiple isolated regions to see how this is meant to be used.

Hello. I did some tests and found that it got broken with the 2.7x series while it was working with previous 2.6x versions. Hope it helps.

It is just how blender works, not a bug. I also find it not really understandable that a display option has an impact on geometry without any warning nor infos in the tooltip. But it's a design task more than a bug. Zero could also completely disable that behavior like in many other cases in Blender (letting objects use the unit system as one would expect)?

Not seeing a bug here on OSX.

If I understand correctly, wasn't able to reproduce this issue.

As far as I can see this is working as expected, are you holding shift the second time you press Z?

I'm not seeing that here.
Can you create a basic polygon on a new .blend and see if it happens there too. (see below)
I suspect there's something else going on.

cut tool creates double vertices that need to be welded afterwards
it happens when i cut middle of the face of the polygonal object.
vertices do not snap to each other,they do not weld automatically sometimes,it creates double overlapped vertices.Knife tool fails to create proper vertices that would not be overlapped,sometimes when the knife tool is being used,overlapped vertexes come up.
I ask if this bug can be resolved,as it is very frustrating to weld each overlaped vertex after using knife tool

@Campbell Barton (campbellbarton) could you take a look at this or assign to someone else that may be familiar with this area? It should be an easy fix, and it's very easy to reproduce.

save and revert - working properly too.
working with bug only without save

i was repeat this error with faces too.
but we have strange behavior:
if we save, close and open again - working will properly

And if I want to implement it, I jsut have to code it and send a send my patch ?

Ok I understand, I guess I will send it. But then, does someone will create a task to implement it ?

Thanks for your interest in Blender, but this is a feature request rather than a bug/patch report. We do not accept such requests here ion the tracker. Those are to be sent to bf-funboard mailing list.

There is no bug, here.

confirmed.
Will also note that neither addon is designed to work on solid mesh.
I think we need to fix this asap.

Could someone please check if this is a bug? Thanks! ;)

Just another update in case it helps - I tested and again and noticed that, after you add the second metaball, if you adjust the "radius" param in the left panel to something like say 0.05, it works super snappy. It's only if you "grab" the radius value w/ your mouse and slide left to reduce the value that I see this issue... and even turning off "continous grab" in the Input settings tab in User Prefs does not fix this.

I am seeing this happening on a much larger scale in Blender 2.78c. I'm running 2.78c on a box w/ an i7 & gtx 1070.

Yeeahhh a big thank YOU Joshua !

There are currently location + rotation keyframes on some of the objects (frames 0 and 33). Try removing all keyframes before fixing the position of all the objects.

Hello everybody. Here is new version with F2 support. Vuk you absolutely rigth, but i don`t have time for this at this moment. Maybe after few days. (where is pyfmt like gofmt :( ).

I would be good to add snapping to loopcut i.e. when you slide egde after hitting CTRL +R and left/right mouse button to accept it could be good to have an option to snap to

Blender 2.8x will change how Surfaces/Curves work.
With these changes a definitive solution can be planned.
In the meantime, this feature will be marked as TODO: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Tools#Transform_Snap

@Duyun Ivan (DIV)
Please when you upload the new version, can use some pep8 style checker like flake8?
Some basic style guide for Blender inclusion:
4 spaces indentation, 2 lines skipped between different functions/classes blocks, spaces around operators, no spaces between equals in parameters assignment, lines must be max 120 chars long.
https://wiki.blender.org/index.php/Dev:Py/Scripts/Guidelines/Addons

Thank for you response. SmartF used point of "Eye View"(point in yours screen) and make face nearest to that point. You must rotate and move camera to control it. And another control is mouse cursor for decision in which direction make face. Offen when you try to make face and can not - it seems like addon fails, but really - it`s bad verts. To check this you need move vert, in this case F2 not fail, because it have not angle/area controls, and it create new fouth vert. If you need this behaviour, just switch off angle control and area control in SmartF and choose square. In triangle mode SmarF don`t create new vert. Anyway, I think it`s not good, but if you wish i can make checkbox in SmarF panel like "Switch to F2" and copy/paste F2 code in function under SmartF. OK, I will send new code for you soon.