No prob at all ! Just note it somewhere in the description
Well , at first glance most of the scripts work fine! And all hotkeys preserved! Great job Kjell!
Only thing I’ve noticed is an error message with Unrotator + Unrot Dup in Object mode atm.
1 Like
confirmed, I had missed that one.
(I actually tested the entire kit. But I did not test every single possible action. I did not have enough sanity-points for that. There might be a few left-over 4.0 bugs ;D)
edit: fixed (quick fix release is now out: 3.06)
edit2: fixed another bug (snapcombo save error) 3.07 (a typo.FML.)
2 Likes
Context Delete:
in 3.05 - there was an error (select multiple polygons, invert selection, then delete)
in 3.07 - can’t delete polygons
can confirm a selection issue , but only with “+” option enabled?
meaning: The issue seems to be with Cut+, (used by context delete)
Hmm… It starts working after some time. But in some cases there are errors:
edit: “+” option was hidden, I didn’t noticed it. It works fine without it (at least after some attempts)
fixed. another hotfix coming up…
edit:
I might attempt to address the ui-issue too, maybe
In certain sizes, some buttons just “dissappear” , oddly enough when there is plenty of space:
Heh, it’s exactly what I was going to post.
Yeah, you’re right, with some width they disappear:
I think it has low-low-low priority.
Found the bug: “align=True” is borked for (row) panel layouts? Should be reported, or has been? Someone else will have to fix that. ed: a bit of edge-case (pun intended) - where you cant have multiple aligns on a row + aligned splits.
ed: fixed (worked-around) 3.08 is out shortly! :X
3 Likes
I’m on 3.6.6 and just updated to 3.08 (Standard) and now I’m getting errors when i switch between presents through keSnapping menus.
Also there is an older bug with Context Bevel. When Auto Apply Scale is Active, clicking Clamp Overlap resets object scale to 1. Here is the gif
- 3.6 is no longer supported (from keKit 3.05 onwards, use 3.04 or earlier for 3.6)
- ah! I was unaware (I habitually apply manually a lot) - fixed. will be in 3.09 or so.
note: will not be in the standard version for some time probably. but you can hotfix-it; overwrite kekit/ops/context_operators.py with this:
context_operators_hotfix.zip (2.3 KB)
1 Like
Hey.
it looks like you have not followed updating instructions 
- Delete the old kekit folder
- Replace the kekit folder with the new
That fixed it. Thank you.
1 Like
Kjell, could you check Frame All or Selected for curves?
It works for Bezier-type curves only in Edit Mode. If any other type or nothing is selected - there is an error. Both B4.0 and B3.6
Confirmed.
And fixed 
Seems like beziers actually shouldn’t have worked, so that might have confused things… (fixed for eventual blender fix now though!)
Will be in the next update, or, I guess this is becoming a habit ; download this hotfix and replace the script in kekit/ops:
ke_frame_all_or_selected_hotfix.zip (1.9 KB)
1 Like
Is it for B4.0 only?
And one more thing.
I’m not sure it’s a proper usage* of QuickMeasure , but if it’s activated in Edit Mode for a curve then it prompts an error and crashes Blender (4.0 + 3.6)
*I wanted to try can it measure the length of a curve
- that fix should™ work on 3.6 too
- QM bug confirmed. It does not support curves other than as “empty” objects in object mode perhaps. No plans to change this. But, ofc it should not crash.
upd: Fixed - will be in next release, or, (Note: this one is 4.0 only) - replace in kekit/ops:
ke_quickmeasure_hotfix.zip (6.1 KB)
1 Like
Frame All or Selected. Tried both 3.6 and 4 - the error fixed.
Not sure is it worth your additional time, but just let you know: for Poly and Nurbs spline types the script isn’t framing selected points:
QM - no errors or crashes! Thank you for the fixes!
No need 
We can convert a curve into a mesh, and use QM - it’ll calculate the length for the ex-curve.
- other curve points: hmm, yes it is unfortunate. seems I need custom code for each curve type (more or less) I’m just go ahead and put that in the maybe file ;>
- qm curve lenghts - same issue as above (not taking “curvature” into account either) ;>