The application will eventually support multiple edit boxes where the subroutines and functions can be opened at the same time in additional edit boxes. The main routine or any of the subroutines or functions could also be opened in multiple edit boxes. This support will be added later, but some preparation work can be done and this will be useful in the reorganization of the program and edit box classes.
Currently there is a list of actions that are built and given to the edit box instance for its context menu. This context menu will only be assigned to the edit box that is currently active and only one edit box will be active at a given time (the one that has focus). When the focus changes to a different edit box, the context menu needs to be removed from the edit box losing focus and added to the one gaining focus. To make this easier, the list of actions are built and stored into a new member variable. This list will be assigned to an edit box instance as needed.
In addition to setting the actions (context menu) of an edit box, the various signals from the edit box needs to be connected to the various actions in the context menu (for enabling and disabling the actions) and to the status bar update slot (for the cursor changed signal). These items need to be done when an edit box instance becomes active. For the edit box losing focus, the context menu (actions) needs to be removed and the signals disconnected.
This code was put into a new edit box set active routine that takes an edit box instance as an argument. Preliminary code was added for first disconnecting the signals and removing the actions of the edit box losing focus. This code was commented since there is currently only one edit box instance.
[commit 5b8741768c]
Saturday, January 4, 2014
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
All comments and feedback welcomed, whether positive or negative.
(Anonymous comments are allowed, but comments with URL links or unrelated comments will be removed.)