[Bf-committers] CTRL-X functionality

Ton Roosendaal ton at blender.org
Wed Apr 25 11:42:24 CEST 2007

Hi Joe,

I didn't know CTRL+X was broken, so what is there to fix, the accident  
someone uses ctrl+x and didn't save?

In my opinion you save work, or you load work, or you quit blender.  
Assuming the user makes accidents bt default is dumbing and slowing  
down UIs.

----> Solve the problems where the problems are, not by adding user  

For example; just save a quit.blend for ctrl+x? There might be more of  
such solutions to prevent the extremely unlikely accident with ctrl+x.

My personal observation: I never (NEVER) in my 12 years of blender  
usage/testing had a Qkey accident, but already got several accidents  
with pressing CTRL+W accidentally. So, probably whatever default you  
pick, it always wrong... we then better move as quick as possible to  
allowing users to tweak keymaps based on own habits.


On 25 Apr, 2007, at 10:57, Doug Ollivier wrote:

> Joe Eagar wrote:
>> Hi.  After reading more discussion of CTRL-X, I've decided that I'm  
>> going to fix it.
>> The best method, imho would be to have CTRL-X popup a menu with 2  
>> entries: "Close Current File (without saving)" and "Close Current  
>> File (save first)".  The menu would be titled "Create New File?".
> and where is "save file as" i'm assuming cancel is not needed because  
> you just click out of the box.
> or does the save file button simply take you to the save dialogue,  
> rather than saves over the current name?
> 1) Don't save
> 2) Save (if first time save. i.e. no existing file then it would act  
> as save as)
> 3) Save as
> Alltaken
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
Ton Roosendaal  Blender Foundation ton at blender.org  

More information about the Bf-committers mailing list