Hi, I don't know. You will have to ask Marco.
Andreas Am 19.02.2014 09:07, schrieb kimaidou: > Hi, > > Another question regarding the embeded groups. Is there any way to tell if > a group is an embeded group with python bindings ? For layers, there is the > layerIsEmbeded method of the QgsProject class, but what about groups ? > > Cheers > > Michael > > > 2014-02-19 9:57 GMT+01:00 kimaidou <[email protected]>: > >> Thanks Adreas for your prompt answer. >> >> 2014-02-19 9:47 GMT+01:00 Andreas Neumann <[email protected]>: >> >> Hi Michael, >>> >>> It is a known issue and Marco Hugentobler is working on it (hopefully >>> still in time for 2.2). >>> >> >> >> Ok. thanks Marco. >> >> >> >>> >>> BTW: you will not be able to rearrange the order of individual layers if >>> you embed a whole group - only the group at a whole. >> >> >> Exactly. I just tried only because of the issue. I won't need it if groups >> and layers are embedded correctly. >> >> >> >>> But the order >>> within the embedded group should be correct once the bug is fixed. If >>> you want to reorder embedded groups or layers you will have to embed >>> them individually several times. >>> >> >> This is what I did to avoid the bug after I discovered it. I recreated a >> group and sub groups with individual embeded layers in them. Then I use >> QGIS project templates to save this state and create new projects with the >> same group. >> >> >> Michael >> >> >> >> >>> >>> Andreas >>> >>> Am 19.02.2014 08:41, schrieb kimaidou: >>>> Hi list, >>>> >>>> Yesterday I played a little bit with the feature "Embed layers or >>> groups". >>>> I works well for single layers, but it seems to behave randomly for >>> groups. >>>> For example, embedding a group containing sub-groups and layers does not >>>> produce the right result in my case : the group is imported, but only >>>> contains the sub-group. All the layers from parent project origninally >>>> contained in the group root are imported in the root of the legend in >>> the >>>> child project. Second problem : the layers are imported with reverse >>> order >>>> compared to their order in the parent project. >>>> >>>> Espected behaviour : >>>> >>>> * imported group >>>> -- * sub-group >>>> ---- * layer A >>>> ---- * layer B >>>> -- * layer 1 >>>> -- * layer 2 >>>> >>>> Actual "buggy" behaviour : >>>> >>>> * layer 2 >>>> * layer 1 >>>> * imported group >>>> -- * layer B >>>> -- * layer A >>>> >>>> And I cannot move the layers 1 and 2 afterwards in the "imported group" >>> as >>>> the embedded groups are read-only. >>>> >>>> Has anyone seen this happen ? >>>> I would be happy to report a bug in hub.qgis.org >>>> >>>> Michael >>>> >>>> >>>> >>>> _______________________________________________ >>>> Qgis-developer mailing list >>>> [email protected] >>>> http://lists.osgeo.org/mailman/listinfo/qgis-developer >>>> >>> >>> _______________________________________________ >>> Qgis-developer mailing list >>> [email protected] >>> http://lists.osgeo.org/mailman/listinfo/qgis-developer >>> >> >> > _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
