Emmanuel Briot 608b498528 Review handling of selection contexts ...

The current context is no longer built on demand. Instead, the view are
responsible for creating the new context whenever it makes sense (for
instance the selection changed), and pass it to the Context_Changed
signal. This lets views decide when a new context should be computed,
rather than let the caller decide.
In particular, editors will be able to update the context only when
the cursor location has changed (and after a short delay), rather than
for every button press signal (to optimize NB19-029).
Rename and simplify the profile for a number of subprograms related to
contexts, in GPS.Kernel.Modules.UI. In particular, the context creation
is always done via a new primitive operation of GPS_MDI_Child_Record,
and the context_func passed to Instrument_Contextual_Menu is now only
used to add entries to the menu, rather than also compute the context.
This context_func will be removed as soon as all contextual menus are
implemented via GPS actions or in the local config menu.

NB19-029 (2/2)

Change-Id: Ib68a848c62bbc20563e95f5a037e1b388a24ed51

2015-01-06 13:57:29 +01:00

..

core

Update copyright notices to 2015

2015-01-05 15:45:56 +01:00

obj

Fix permissions

2009-11-23 20:11:05 +00:00

src

Review handling of selection contexts

2015-01-06 13:57:29 +01:00

.cvsignore

Fix permissions

2009-11-23 20:11:05 +00:00

python_core.gpr

Remove references to gtk from common.gpr

2013-09-12 13:42:56 +00:00

python.gpr

Merge changes from trunk.

2013-02-21 16:37:08 +00:00