@William Reynish (billreynish), , as Andy Davies said, maybe it is inconsistent with interactive tool, but it is a very big regression and worse to not have it and have interactive tool than vice versa.
I tried for a very long time to deal with it , but can not. It is a straggle with history repeat, when it was earlier it was good.
@Brecht Van Lommel (brecht), @Campbell Barton (campbellbarton) could you give us a line of code and where to put it to bring back (change to) "old" good functionality of bevel, inset tool?
those who want it back apply code to have it, for the rest it stay as it is. I dont want to wait until perhaps it will be in 2.80

Could you bring back the functionality of previous version? - I mean the way of selecting --> earlier you could hoover mouse over and drag to select/ deselect or with ctrl click. Now you only can do it one by one click which is very annoying

#brecht , the problem still exists. tried on #9a5df92c1bd
when I do steps 5-6 and then do smart uv project, it is ok, but when I do steps 5-7 then the result is as in step 8. It should add another cube but in cm not meters( or if it does it in meters then smart uv should work in island margin 100x more).
Also when I open older scene created in 2.78 which at start was set to metric/cm and try to do smart uv then island margin changes very little.

andy davies, I am with you and also very please devs to do inset/bevel userfriendly as it was earlier.

@Brecht Van Lommel (brecht) some time has passed. I accepted new behaviour of bevel/inset value. But working with this is slower and less effective.
history list has some amount of items and very often you cannot repeat previously used command because it is not in history list. and you have to set the desired value from scratch. It would be a lot more better to have behaviour as earlier -shortcut to bevel/inset remember the value or if it cannot be in that way, then have option in F6 panel to remember value.
All users would have then choice how they want operator to work

Ok, I understood. thank you. Two things haunt me:

1. shift+r works if you are doing bevel one after another - you repeating just last command, and it is fine with this case
2. history F3 is also good, but what if there are so many commands after bevel that it is not in history list ( or is but there are so many commands you have to find bevel instead just clicking ctrl+b) and you want to do bevel with previous amount you dont remember?

Hi Brecht, nothing has changed. I tried in official 2.79a, 2.79 c169454 and official 2.78c. In 2.78 it works and in 2.79 not. So here are the steps to check it:

1. shift+a to add cube
2. tab to edit mode cube, select some edge and ctrl+b to bevel with mouse move
3. select other edge and ctrl+B to bevel

Alberto, did you read all the post from the very begining?As LazyDodo wrote, try it. And of course there is no any option to remember bevel amount(that is why you googled it only in this thread). I only talk about how blender works in itself. If you in F6 in 2.79 set some amount then when you do bevel, it remember the set value. and there is no option to check "remember value". in 2.79a it does not work that way as in 2.79. simple, clear now?

Alberto, it is not the same behaviour since 2.5 because in 2.78.4 it works good( remember bevel amount set it menu F6). No, you cannot repeat the bevel with shift r if you go out of edit mode. And repeat history is solving problem around and is 1 more step to do bevel with previous setting. And that is the problem, bevel does not remember bevel amount.

I suggest to provide a feature in bevel settings e.g. "reset values" for those users who like to remember all the settings in all operators and set them manually every time

the problem still occurs in latest build 9b29233

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

I would like to spot that this is very old issue and very important and basic in modelling(but unuseful in this form right now). Please devs to make the thing works as expected

it happens when you try to "bridge egde loops" ( W, G) two faces

I do not have the crash in blender 2.70a on win xp 32

I think there is something wrong yet with it.
the same file.
-gg slide edge loop for some distance to right side
-check "Correct UV" in left panel
-gg slide edge loop for some distance to left side
-uncheck "Correct UV" in left panel
-check "Correct UV" in left panel

ok, I understood

when I read tip which shows after I am pointing out on select interior faces :" select faces where all egdes have more than 2 face users" I understand it as in example below. Face in center of each of two cubes is interior( edges have more than 2 face user), so why this function works only in left one? Am I wrong?

I have made shortcuts from scratch in ee5936c (version 2.72 #427) because something was wrong with "copying previous" after v 2.71.
Then I downloaded 33f388d (#441) and problem with shortcuts occured. I resolved it in 6c2ce7a (#447), I do not remember if it worked then already or if I just set this one shortcut "G" once more. I work now on 6c2ce7a (#447) with user pref saved in this version but with startup.blend from ee5936c (#427).
What is weird that when I open ee5936c (#427) shortcut G does not work. It does not work with startup.blend from C:\Documents and Settings\{username}\AppData\Roaming\Blender Foundation\Blender\2.72\startup.blend made with.
I have to drop the same startup.blend to start working ???!!! Or load factory settings and then drop startup.blend or userpref to work.
With the newest version d434815 (2.73 #663) copy previous settings also does not work.
To make it work I have to change by myself shortcut G

Yes, it happens with 2.73a

it still occurs , checked in 59e2f91

I would like to suggest another functionality to loopcut - loopcut on selected.
Now if we have mesh like on image screen1 {F132449}it is not possible to make loop cut in selected egdes at once. We have to subdivide them and then select and move/slide.
If we had an option "on selected" we could do it very fast and better .

I checked the behaviour in 6c2ce7a ( #447), that means in default settings I turned off translate with LMB/RMB and drag, save user settings, run blender version ee5936c and the problem still occurs. The quick solution is, after copy previous settings, just to set once more shortcut for translate "G" , but what if other shortcuts made from scratch in ee5936c, does not work well in next versions.

the same problem with #441 - 33f388d

I have just checked it with default settings. open blender #427 , turn off translate with LMB/RMB and drag, save user settings, save startup file. close blender #427, open blender #439 and the same problem. mess with translate shortcuts

for #427 ee5936c, for #439 560dd93.

I have made a research and it is as follows:

1. in factory settings when I take and drop my startup blend file into 3d view everything works perfect. but when I then save startup file and reopen blender the problem comeback.
2. after some time of trials I came up with a solution
   • • in factory settings I take and drop my userpref blend file into 3dview , load my keyconfig file, and then save user settings.
   • reopen blender and save startup file. And it works as it should be.

but there is nothing special in my settings, just different colours of UI, some shortcuts and arrangement of panels.In one word - only the look There was no problem in blender 2.71 build 1477- the latest I have that works. I have no idea what causes problem, maybe something happened with startup file with 2.72

it happen also with other mesh without array modifier.
I tried to remodel some parts of that mesh - change the topology of tris and it helped.
but it should be a reason for such strange behaviour

ok. there it is{F115236}

I have tested and cannot find what cause the issue. When I opened blender, made simple mesh from box, detached couple of faces, then join them and made 'remove doubles', blender crashes. But later with the same actions, with reopening blender, it did not happen any more. So leave it for now as 'secret factor'.

I did not have time to test and find logical steps with this issue. As I noticed it is now unpredictable, I will try to test this weekend and give some info

I think it would be better if tabs were on the right side of toolbar instead of the left. If you want to choose some tool you should firstly set the proper tab then the tool. Now you have to move mouse cursor over the hole width of toolbar, select the tab, and back again to toolbar. I think there is too long path to get the wanted tool.

The problem does not occur any more. I checked on Win XP x64, ATI x1900GT and Win 7 x64 , Quadro FX 1700. blender build from 18th december

THANK YOU BRECHT :) I changed the color space of alpha input and it works as expected. Now I can go further...

I did what you have adviced, brecht ( if I understood you well). But the problem still occurs. The final alpha channel of the image after connecting file F.png and F_a.png is not the same as the original file F_a.png. If you could set the right node setup to achieve the expected result I would be grateful.

in official 2.69 from blender.org r60995 it works and there are no crashes

for me it still does crash blender. I tried r61240 win x64 from builder.blender.org