[GRASS-user] d.mon displays box on startup

[Huidae Cho]

Maybe, this figure is easier to understand. blue for comp region and red
for partial version.

Black: display
Blue: full comp region
Red: partial intersection of display and full comp region

In this color scheme, it's very clear what we're looking at in the display.

[image: image.png]

Huidae


On Mon, Dec 24, 2018 at 9:06 AM Huidae Cho <grass4u at gmail.com> wrote:

> So how does it work now in one color?
>
> 1. display == full comp region: red box
> 2. display > and contains full comp region: red box smaller than display
> 3. display < and inside full comp region: no box at all? (can be confusing
> with cases 4 & 5) or red box (can be confusing with case 1). I think we
> need two colors in this case? Actual comp region borders red, Display
> borders within comp region blue (maybe, switching blue and red would be
> better?). For example, completely inside (not crossing any comp region
> boundaries) blue box. Looking at the east comp region boundary: vertical
> line in red, top-left, bottom-left, and left in blue. Again, I think if we
> use red and blue, it would be better to use blue for comp region borders
> and red for partially/contained borders.
> 4. display > and does not contain full comp region: no box
> 5. display < and outside full comp region: no box
>
> Huidae
>
> On Mon, Dec 24, 2018 at 7:02 AM Martin Landa <landa.martin at gmail.com>
> wrote:
>
>> Hi,
>>
>> st 26. 9. 2018 v 20:27 odesílatel Anna Petrášová <kratochanna at gmail.com>
>> napsal:
>> > I think it changes color depending if you are zoomed inside or outside
>> of the region. I find this behavior little bit confusing, perhaps just
>> having one color would be enough, and maybe don't show it when you are
>> zoomed inside?
>>
>> in r73826 the settings was changed to show comp. region extent in red
>> color only regardless display and computation extent position. If no
>> objection I will do backport to g76 release branch in next days.
>> Question is whether comp. region extent should be displayed by
>> default. The behaviour has been changed accordingly [1], but
>> unfortunately there was no feedback. Any opinion (since it affects
>> 7.6.0 release)?
>>
>> Ma
>>
>> [1] https://trac.osgeo.org/grass/ticket/3519
>>
>> --
>> Martin Landa
>> http://geo.fsv.cvut.cz/gwiki/Landa
>> http://gismentors.cz/mentors/landa
>>
>
>
> --
> Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE
> Open Source GIS Developer, GRASS GIS Development Team
>


-- 
Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE
Open Source GIS Developer, GRASS GIS Development Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20181224/5ccb878b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 13157 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20181224/5ccb878b/attachment-0001.png>