Why is it that the entire context (ie: 3D view global) needs to be edited to just change one or two keys? This results in default (inbuilt) key changes to blender not being propagated to existing default .blend, even when the changes don't touch the exact operator you changed.
Wouldn't it be better if you could edit just one hotkey and leave the rest default (unedited) even on the same context? Daniel Salazar 3Developer.com On Mon, Jul 11, 2011 at 4:57 PM, Martin Poirier <[email protected]> wrote: > They also need to be able to remove entries from keymaps, not just add > entries or overwrite entries. > > Martin > > --- On Mon, 7/11/11, Matt Ebb <[email protected]> wrote: > >> From: Matt Ebb <[email protected]> >> Subject: Re: [Bf-committers] Keymap storage & management >> To: "bf-blender developers" <[email protected]> >> Received: Monday, July 11, 2011, 6:36 PM >> On Tue, Jul 12, 2011 at 1:51 AM, Ton >> Roosendaal <[email protected]> >> wrote: >> >> > >> > - The "Preset" map is not only to mimic other maps, >> but can be used >> > for cases like "2.4 power user map" or "Optimal Laptop >> map" as well. >> > This will be in our distros. >> > >> >> One note: keep in mind for these sort of presets to work >> properly, they need >> to encompass more than just key bindings - they also >> need to control things >> like zoom and orbit styles, 'release confirm' setting, >> etc.. >> >> cheers >> >> Matt >> _______________________________________________ >> Bf-committers mailing list >> [email protected] >> http://lists.blender.org/mailman/listinfo/bf-committers >> > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
