-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Pluginlegend customize #294
Conversation
Customization settings used are the same as the Layer menu ones. TODO : add subtree in Docks/Legend customization to separate customization
- Adv Labeling option to 'Show upside-down labels': never, when rotation defined, or always - 'Never' (default) option is same as before, labels with 90 <= angle < 270 are turned so their text is always upright - 'When rotation defined' option shows upside-down labels if their rotation is layer- or data-defined (dynamic labels are turned upright) - 'Always' option shows upside-down labels at layer- or data-defined rotations and for dynamic labels
…pluginlegend_customize
A plugin should call addLegendLayerAction to add action. Example : self.iface.legendInterface().addLegendLayerAction(self.action_to_add, "plugin_name", string_id, QgsMapLayer::LayerType ) add an action under a submenu named "plugin name" Signed-off-by: Hien TRAN-QUANG <hien.tranquang@gmail.com>
…xt menu of a layer/group of layer. Signed-off-by: Hien TRAN-QUANG <hien.tranquang@gmail.com>
I am going to close this pull request, for a few reasons 1- you removed the work I had done in layerlegend_customize now may I ask why you discregarded a number of my commits, instead of adding commits after? This results in a waste of time for everyone. thanks |
Hien can you please add any changes (after my commits) to the correct branch - layerlegend_customize thanks |
Hello, Sorry I think I have messed up something when I fetch your commits and I'm going to restart from your commits and add commits after. Just a few questions :
Just checking your code, it seems we worked on two parallel branches : for Can you tell me which part I can contribute to, so I don't mess things up Thanks Hien. 2012/10/15 Etienne Tourigny notifications@github.com
|
In addLegendLayerAction it is preffered to add the plugin name, just to make sure there are no clashes, but there is no enforcement. The menu name is optional, and can be different from the id which should be unique. For example, menu name can be translated with tr(), but id should not, it's internal to the plugin design. I was always working on my layerlegend_customize branch, after pulling from your branch. No need to have 2 branches because these are related features, the plugin customization requires your legend customization. Please add any fixes/enhancements there. What is missing is the customization part (selecting which ones are visible or not). If you prefer I will add that and you can review, but I will not have time before tomorrow. thanks |
Ok, I understand now. I don't know yet if I'll get time to modify the customization part before Thanks. Hien. 2012/10/16 Etienne Tourigny notifications@github.com
|
Hello,
I created a new branch to allow customization of plgins in the legend dock.
The plugin should call as in your test plugin (I changed the id to make it more simple):
self.iface.legendInterface().addLegendLayerAction(self.action_add_sel_tiles, "Tile Index", "addSelTiles", QgsMapLayer.VectorLayer )
in order to be enabled.
In customization dialog, it will appears under Docks/Legends/Plugins//
On a right-click on a layer, a submenu named will regroup the actions.
Can you test it and give me a feedback ?
Hien TRAN-QUANG