Hi,
I would also prefer the tooltip to be optional. For my work (mostly small and
medium scale historical, physical and political maps) the tooltip is not really
necessary. If I want to check the number of items in a layer I normally use the
Crtl+A command.
Regards,Andrei
On Wednesday, March 25, 2015 6:42 PM, Giuseppe Aruta
<giuseppe_ar...@yahoo.it> wrote:
Going back to to differentiate Layerable
The list should be:
- Layer.class
a) layers which already have a datasource
b) layers with no datasource (layers in memory)
c) layers of type a) which have been modified and not saved
d) layers of type b) which have been modified and not saved
- RaferenceImage
no need for now to distinguish as we don't have referencedImage layer which are
only in memory. It depends on what we want to do with this types of layer
-RasterImageLayer
Before Alberto modifications there was a problem as we used to have
a) Images with datasource
b) Images with no datasource (WarpImageToFence and ExportPartOfImge plugins).
It was not a big problem as only two Pirols plugins were involved. Note that OJ
still didn't have an option on "Closing Project/Program" that warn users if a
"Sextante Raster Image Layer" was in memory or not.
After Alberto's modifications all Raster Layer are saved to OS/TEMP(*) folder
so there is no need of that warning. So we only have option a)
(*) I am going to modify this and introduce an option to set a default output
raster folder, like in GvSIG. And a unique ID to add to ouput temporary files
(like in Kosmo) to prevent a) to loose files in TEMP folder if user is not
aware and shut down the PC (expecially in Linux/MacOSX), b) to overwrite
existing files with the same name (the actual used method LayerManager.class
uniqueLayerName(String name) seems to have a problem with Raster layers loaded
via Sextante)
2015-03-25 16:31 GMT+01:00 <edgar.sol...@web.de>:
On 25.03.2015 16:23, Michaël Michaud wrote:
> First of all, I fully understand your initial need to differentiate in-memory
> layers from persistent layers. I also need this feature and thought that we
> could achieve it using different font/color/background...
> Not so easy indeed as it may be combined with editable bold, red)/selectable
> (italic) information.
> Maybe we could use a different background for persisted layers (or just
> write them with a bold font...). It would not be too difficult to test.
> Another (more complex) solution would be to add a column in the layer
> name panel : datasource icon (+ tooltip for name) / style icon / visibility
> checkbox / name
common desktop software uses an asterisk after the file name eg. my_file.txt*
to signal that this file has unsaved changes.
we could do the same after the layer name. .. ede
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
