-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Menu Actions in general #1
Comments
If/when you have any time for it, feel free to help fill in the table above. I'll gradually plug on it, too. To edit, click the ... button in the top right of the post, then Edit, et voila. Note there is a Preview tab next to the Write tab in edit mode to see your edits before saving, if desired. |
Sorry , I missed this email. I'll try tomorrow. |
Concerning your LG questions, I've got a slight problem at the moment. A bug was introduced in the last TM update. rgrds marios |
Yeah, I had the same problem on my late 2011 MBP when updating to TM version 2.0.17. They fixed it in 2.0.18, but it is not immediately clear. The latest version is 2.0.19, though, so make sure you have that first. When you first open the bundle editor, after updating to 2.0.18, the editor will appear like your image. You just have to pull down the file browser pane to see it. Put your cursor right on the bottom line of the top frame. You should see a window pane icon appear somewhere when you have the position right. Then just drag that down to open up the file browser. After that it stays put. ;) |
There is no rush on these issues. We just fiddle when we have the time. Somebody will come along eventually. I suspect once the community starts focusing on Textpattern themes more (probably after unlimited custom fields land), this bundle might get more attention. |
There are a lot of them, which may not be bad, but it also might be worth considering them all in terms of what people really want/need to bother having in the menus. I mean, if you can type a Txp tag faster than it takes to find an action in a big two tier menu, then we should want to find a better balance there. So with that, some thoughts on the current state of menu actions:
excludeItems
array without removing their files or changing the menu structure. (There's an example of such an array in the Textile.tmbundle's info.plist file.) It's basically the same idea as hiding them until further notice. This might be a good idea for broken actions, or ones that are deemed less desirable.The following table is a work-in-progress to map actions and their status as they appear in the bundle's main menu. Once complete, it's easier to make global decisions about what actions to keep or not, and which ones need specific issues for fixing, whether to edit menu strings, shortcuts, or actions themselves.
Table 1. Mapping of menu actions.
<txp: />
The text was updated successfully, but these errors were encountered: