The map list and it's order :) I knew this will be subject for discussion one
day.
------------
Let me explain a bit of the background. In QLGT the database objects for all
items where separated from
the tool views and the canvas. Resulting in quite some effort to synchronize
all that stuff. And making it
very very hard to work with multiple instances.
Getting more familiar with QT's tree widgets I found it the perfect solution to
this problem. The tree widget
_is_ the toolview and the database object for items to be displayed. This
applies to the map list, the DEM
list and the workspace list. The tree widget items are the items to be drawn.
In the tree widget the tree
widget items keep all the data about the item to be drawn. It will display it's
state and setup. Together with
a draw context it will render it's content.
The draw context's thread will simply read from the first item in the list to
the last and call it's render
method. Thus the order of the items influences the draw order. First comes
first.
When I started I thought several views are perfect to handle several different
maps for the same area.
Funny enough I only have one view with all those maps I frequently use. The
list reminds me of my old class
room. We had multiple maps fixed as scrolls on the ceiling and the teach was
pulling down what ever was
needed. If I need another map in QMS I simply do the same. I pick it with the
mouse and drag-n-drop it
down to the bottom of the list. A movement very similar to what we have done in
the class room. And
much easier than switching views.
----------------
That explained it should be obvious why the map is moving in the list. And that
a fixed order is not possible.
It can be discussed if a map deactivated should be sorted back into the list of
deactivated maps or stay on
top. I didn't care so far.
Another thing I thought about myself, too, is saving a certain map scenario to
a file. Sometimes I
accidentally close my view and have to restore my list of active maps.
I think it's a big step to usability to simply define paths to the maps and not
to manually register every
single map. You throw a single file into the folder and you will see it in the
list. Even the vrt thing is too much
for many, but I can't help it. I would need to publish own maps to avoid that
bit of a hassle.
In comparison to QGis: I hate the way QGis is managing maps and data. Probably
I would have stopped to
develop my own software if the way QGis is handling things wouldn't have driven
me nuts. But I am sure it's
way is perfect for dealing with scientific projects that need a highly
configurable way to display data.
Together with the python interface a very powerful tool. But not for users of
consumer products.
--> I add an issue to save the active map list.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
Qlandkartegt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
