Maciej Suminski 75fb04d650 TOOL_ACTIONs are handled with transitions, no handlers needed in the event loops ... There used to be a number of TOOL_ACTIONs that had entries both in SetTransitions() and the event loop, which seemed redundant and troublesome. Now it is not necessary anymore, transitions setup is enough to execute associated actions.		2017-01-18 14:20:39 +01:00
..
action_manager.cpp	Replace BOOST_FOREACH with C++11 range based for.	2016-06-29 16:07:55 -04:00
context_menu.cpp	Replace boost::function and boost::bind with their std:: counterparts	2016-06-29 12:23:11 +02:00
tool_action.cpp	Fixed an assert when footprint viewer was closed before the pcbnew window.	2015-07-28 10:29:00 +02:00
tool_base.cpp	TOOL_SETTINGS acquires wxConfigBase each time it is used.	2015-08-07 18:17:51 +02:00
tool_dispatcher.cpp	Replace BOOST_FOREACH with C++11 range based for.	2016-06-29 16:07:55 -04:00
tool_event.cpp	Split the undo/redo event into the two stages "pre" and "post" for convenient synchronization of dependent state.	2016-09-23 13:29:25 +02:00
tool_interactive.cpp	Add coroutine call invocation context to identify the main stack frame.	2016-09-21 11:56:40 +02:00
tool_manager.cpp	TOOL_ACTIONs are handled with transitions, no handlers needed in the event loops	2017-01-18 14:20:39 +01:00