how about - layers without datasource ** (are probably created during runtime, so there is a probability that the user wants to save those) - layers with datasource and unsaved change * - layers with datasource and no unsaved change (nothing, cause all is well wrt. to these)
..ede On 25.03.2015 19:33, Michaël Michaud wrote: > Hi, > > Using an asterisk after the layer name could be a way to go, but which > one would you mark ? > Initially, we wanted to recognize no-datasource layers, but the usual > way of using * would > suggest to include also layers with datasource and unsaved change ? > - layers without datasource > - layers with datasource and unsaved change > - layers with datasource and no unsaved change > > Michaël > > Le 25/03/2015 16:31, edgar.sol...@web.de a écrit : >> 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
