Can you try to compile from this source code branch? https://github.com/qgis/QGIS/tree/release-2_18 just to be sure that the issue has completly fixed.
regards Luigi Pirelli ************************************************************************************************** * Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com * LinkedIn: https://www.linkedin.com/in/luigipirelli * Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli * GitHub: https://github.com/luipir * Mastering QGIS 2nd Edition: * https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition ************************************************************************************************** On 18 May 2017 at 10:31, Hernán De Angelis <[email protected]> wrote: > Thank you for your fast response, Luigi. > > I understand. I can wait for the next release, no problem. As for the > <someValue> question, I will have a look and come back with whatever I find, > but when I found this I wasn't working on any particular project nor using > composer either. > > Cheers > > Hernán > > > On Thu, May 18, 2017 at 10:12 AM, Luigi Pirelli <[email protected]> wrote: >> >> fixed during the hackfest on current 2.18 code (you have to wait for >> 2.18.8... or update to the latest 2.18 code not the tagged release >> version) >> https://github.com/qgis/QGIS/pull/4306 >> and 3.0 >> https://github.com/qgis/QGIS/pull/4444 >> >> btw there are some simple workaround to fix temporarly waiting the patch >> release >> >> workaround 1) in the attribute table, apply a sort on some column => >> apply sortOnTop >> workaround 2) in your project xml file you should have a tag as: >> <attributetableconfig ... sortOrder="<someValue>" > >> in your case <someValue> is something different from 0 (Ascending) or >> 1 (Descending)... fix it and sortOnTop will be back :) >> btw, pelase let me knwo what value is in <someValue>, because is not >> clear who's set it to a strange value (probably the composer) >> >> cheers >> Luigi Pirelli >> >> >> ************************************************************************************************** >> * Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com >> * LinkedIn: https://www.linkedin.com/in/luigipirelli >> * Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli >> * GitHub: https://github.com/luipir >> * Mastering QGIS 2nd Edition: >> * >> https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition >> >> ************************************************************************************************** >> >> >> On 18 May 2017 at 10:03, Hernán De Angelis <[email protected]> wrote: >> > Hi >> > >> > Yesterday I compiled from source QGIS 2.18.7 in openSUSE Leap 42.2 >> > Linux. >> > Everything went fine and there were no problems with the compilation. >> > However, when using the new installation I realized that the function >> > that >> > allows to move the attribute row of a selected feature to the top of the >> > attribute table does not seem to work. This problem was not present in >> > my >> > previously installed version (2.18.6), nor in another machine I use >> > (QGIS >> > 2.14.2, Windows 7) using the same data. I wonder if any other users are >> > experiencing this in 2.18.7, or there is just something wrong with my >> > particular installation. >> > >> > Regards, >> > >> > Hernán >> > >> > >> > _______________________________________________ >> > Qgis-user mailing list >> > [email protected] >> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user >> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > > _______________________________________________ Qgis-user mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
