<div dir="ltr">Hi Martin,<br><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 22, 2014 at 9:57 AM, Larry Shaffer <span dir="ltr"><<a href="mailto:larrys@dakotacarto.com" target="_blank">larrys@dakotacarto.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Martin,<br><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks for the quick fixes. All of my reported issues were addressed. The reported funky connection issue appears to be my mistake. I believe I must have had a layer still in edit mode somewhere in the legend when I thought there was none. Could not reproduce that issue.<br>
<br></div><div class="gmail_extra">However, I did notice that the new legend is not quite the same as the old. You can now edit the name of the layer directly with a click-hover. Very nice!<br></div></div></blockquote><div>
<br></div><div>Hmm. While that feature is nice, it is a little too easy to rename a layer. For example, double-clicking the name of a legend layer to bring up properties (if set in Options) leaves the layer name in an editable state. Upon closing the properties dialog, any keyboard input changes the layer name in the legend, because the keyboard focus is still active there.<br>
<br></div><div>Maybe ensure the name is not editable when a double-click is detected? While that would fix the noted issue, it doesn't address how often the layer's name becomes unintentionally editable during normal legend use.<br>
</div><div><br></div><div>Any ideas on how to leave the mouse-activated name changing but reduce unintentional editing?<br><br></div><div>Regards,<br><br></div><div>Larry<br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"></div><div class="gmail_extra">
Geez, all that work and only one small new feature? :-)<br><br>Thanks again for upgrading the previous legend's tangled and limiting code. Looking forward to the new features and usability this will bring.<br clear="all">
</div><div class="gmail_extra"><div><br></div><div>Regards,<br></div><div><br>Larry</div><div><div class="h5">
<br><br><div class="gmail_quote">On Thu, May 22, 2014 at 12:42 AM, Martin Dobias <span dir="ltr"><<a href="mailto:wonder.sk@gmail.com" target="_blank">wonder.sk@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi Larry<br>
<div><br>
On Thu, May 22, 2014 at 2:39 AM, Larry Shaffer <<a href="mailto:larrys@dakotacarto.com" target="_blank">larrys@dakotacarto.com</a>> wrote:<br>
> Hi Martin,<br>
><br>
> Thanks for your work on this and for the sponsors that supported it!<br>
><br>
> Couples things I noticed:<br>
><br>
> * There is no longer and indication that a layer is in edit mode, or not,<br>
> i.e. the edit pencil icon, and its relative states (red or yellow), is gone.<br>
><br>
> * There is no longer an indication of the active layer, previously the one<br>
> underlined. This is different than the currently selected layer(s). The<br>
> underline would persist with no selection, or multiple selections, and would<br>
> mirror the view's currentItem(), or in maybe now currentIndex(). When<br>
> iface.activeLayer() is used in console, it should return the identical layer<br>
> in the legend that is underlined, or otherwise indicated as active.<br>
><br>
> * Something is funky with the connections between the legend and the Current<br>
> Edits functionality. After a layer is no layers are editable anymore, the<br>
> submenu is still active, offering to cancel edits. I added that code, and<br>
> can investigate more after the feature freeze.<br>
><br>
> * There is no longer a tool tip when hovering over the layer, showing the<br>
> layer's source definition.<br>
<br>
</div>Thanks a lot for the feedback. Will address that shortly.<br>
<div><br>
<br>
> * When opening one project, QGIS crashed with the following (project never<br>
> loads):<br>
><br>
> Exception Type: EXC_BAD_ACCESS (SIGSEGV)<br>
> Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010<br>
><br>
> 0 org.qgis.qgis2_core QgsSymbolV2::drawPreviewIcon(QPainter*, QSize) + 42<br>
> (qlist.h:99)<br>
> 1 org.qgis.qgis2_core<br>
> QgsSymbolLayerV2Utils::symbolPreviewPixmap(QgsSymbolV2*, QSize) + 114<br>
> (qgssymbollayerv2utils.cpp:517)<br>
> 2 org.qgis.qgis2_gui<br>
> QgsLayerTreeModel::addSymbologyToVectorLayer(QgsLayerTreeLayer*) + 570<br>
> (qgslayertreemodel.cpp:520)<br>
> 3 org.qgis.qgis2_gui<br>
> QgsLayerTreeModel::addSymbologyToLayer(QgsLayerTreeLayer*) + 88<br>
> (qgslayertreemodel.cpp:480)<br>
> 4 QtCore QMetaObject::activate(QObject*, QMetaObject<br>
> const*, int, void**) + 2141<br>
> 5 org.qgis.qgis2_core<br>
> QgsLayerTreeLayer::registryLayersAdded(QList<QgsMapLayer*>) + 307<br>
> (qgslayertreelayer.cpp:145)<br>
> 6 org.qgis.qgis2_core QgsLayerTreeLayer::qt_static_metacall(QObject*,<br>
> QMetaObject::Call, int, void**) + 172 (qlist.h:731)<br>
<br>
</div>Oh, sorry about that. Something must have gone wrong with a vector<br>
layer's symbol. I can't see where the problem could be straight away -<br>
would it be possible for you to send me the project file - or see if<br>
you can provide more information how to replicate the problem?<br>
<br>
Regards<br>
<span><font color="#888888">Martin<br>
</font></span></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div></div></div>