On Tue, Mar 24, 2015 at 5:31 PM, Daniel Victoria <[email protected]> wrote: > Hi Radim, > > Is this why my QGis crashes when i try to load a Grass 7.0 vector file? [1]
AFAIC, it should only crash if you try to open a GRASS mapset with GRASS 6 vectors in QGIS browser compiled and run with GRASS 7 provider. It is described here: http://lists.osgeo.org/pipermail/qgis-user/2015-March/031177.html I think that I know already what the problem is. If GRASS 7 lib is tries to open a vector which it is not in format 7, it calls G_fatal_error(), which normally opens a warning dialog. Because items in the browser are populated in threads, it happens on non GUI thread, but to open a dialog with an icon, it has to use QIcon which can only be used on GUI thread. Radim > Thanks > Daniel > > [1] - > http://gis.stackexchange.com/questions/138477/loading-grass-7-0-vectors-in-qgis-broken > > On Tue, Mar 24, 2015 at 11:47 AM, Vaclav Petras <[email protected]> > wrote: >> >> On Tue, Mar 24, 2015 at 5:56 AM, Radim Blazek <[email protected]> >> wrote: >>> >>> >> Are there functions in time series implementation which need to be >>> >> called directly from the plugin or everything may be done just calling >>> >> t.rast.* modules? >>> > >>> > Most of the temporal functionality is available through the temporal >>> > modules. However some important algorithms (temporal re-sampling) are >>> > available only in the Python framework. This is needed for time series >>> > animation creation. Using the framework directly will speed things up, >>> > because the module calls, the parsing and interpretation of the module >>> > outputs can be avoided. >>> >>> If it should be used for dynamic animation in QGIS canvas you could >>> consider the possibility to subclass raster renderer in Python and >>> insert it into raster layer pipe from Python plugin. >> >> >> Speaking about animations, some things from GRASS GIS GUI could be perhaps >> used directly in the same was as Tcl/Tk NVIZ is used in processing for GRASS >> 6. Animation tool is one of them. This would be great since we would get al >> least some functionality/code sharing between GRASS and QGIS GUIs which is >> otherwise not possible due to Python/wxPython and C++/Qt (and would be only >> possible if both things would be at least in the same language). >> >> This is of course not fulfilling the requirement to be general, i.e. work >> with other data providers in QGIS, but surely some things just have to be >> like that if they are using GRASS-specific formats (temporal data) or >> algorithms (e.g. algorithms to work with temporal data, their topology, >> ...). >> >> Vaclav >> >> _______________________________________________ >> grass-user mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/grass-user > > _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
