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

2018-12-27 Thread Veronica Andreo
Hi Huidae,

El jue., 27 dic. 2018 22:17, Huidae Cho  escribió:

> Hello Vero,
>
> Actually, 3b has a complete rectangle (NW in red, SE in blue)
>

Right :)
I overlooked the blue part. Still, IMHO, case 3b it's confusing.

Best,
Vero


On Thu, Dec 27, 2018 at 7:24 PM Veronica Andreo 
> wrote:
>
>> Hi all,
>>
>> +1 for showing computational region by default! It is a super handy
>> feature :)
>>
>> Regarding the different colors, I do not have a very strong opinion. I
>> was already used to blue for full region extent coincident with display and
>> red when display is different from region extent.
>> Case 3b proposed, IIUC, would mean that display will have incomplete
>> lines and that seems more confusing in my view. I would suggest that (if
>> implemented like this) 3b is shown as 3a.
>>
>> my2cents
>> Vero
>>
>> El lun., 24 dic. 2018 a las 15:30, Huidae Cho ()
>> escribió:
>>
>>> 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  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 
 wrote:

> Hi,
>
> st 26. 9. 2018 v 20:27 odesílatel Anna Petrášová <
> kratocha...@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
>>> ___
>>> grass-user mailing list
>>> grass-user@lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/grass-user
>>
>>
>
> --
> Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE
> Open Source GIS Developer, GRASS GIS Development Team
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-12-27 Thread Huidae Cho
Hello Vero,

Actually, 3b has a complete rectangle (NW in red, SE in blue).

Regards,
Huidae


On Thu, Dec 27, 2018 at 7:24 PM Veronica Andreo 
wrote:

> Hi all,
>
> +1 for showing computational region by default! It is a super handy
> feature :)
>
> Regarding the different colors, I do not have a very strong opinion. I was
> already used to blue for full region extent coincident with display and red
> when display is different from region extent.
> Case 3b proposed, IIUC, would mean that display will have incomplete lines
> and that seems more confusing in my view. I would suggest that (if
> implemented like this) 3b is shown as 3a.
>
> my2cents
> Vero
>
> El lun., 24 dic. 2018 a las 15:30, Huidae Cho ()
> escribió:
>
>> 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  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 
>>> wrote:
>>>
 Hi,

 st 26. 9. 2018 v 20:27 odesílatel Anna Petrášová 
 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
>> ___
>> grass-user mailing list
>> grass-user@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-user
>
>

-- 
Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE
Open Source GIS Developer, GRASS GIS Development Team
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-12-27 Thread Veronica Andreo
Hi all,

+1 for showing computational region by default! It is a super handy feature
:)

Regarding the different colors, I do not have a very strong opinion. I was
already used to blue for full region extent coincident with display and red
when display is different from region extent.
Case 3b proposed, IIUC, would mean that display will have incomplete lines
and that seems more confusing in my view. I would suggest that (if
implemented like this) 3b is shown as 3a.

my2cents
Vero

El lun., 24 dic. 2018 a las 15:30, Huidae Cho ()
escribió:

> 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  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 
>> wrote:
>>
>>> Hi,
>>>
>>> st 26. 9. 2018 v 20:27 odesílatel Anna Petrášová 
>>> 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
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-12-24 Thread 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  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 
> wrote:
>
>> Hi,
>>
>> st 26. 9. 2018 v 20:27 odesílatel Anna Petrášová 
>> 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
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-12-24 Thread Huidae Cho
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  wrote:

> Hi,
>
> st 26. 9. 2018 v 20:27 odesílatel Anna Petrášová 
> 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
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-12-24 Thread Rich Shepard

On Mon, 24 Dec 2018, Micha Silver wrote:


I'd like to see the region displayed by default. Usually the first thing I
do is show the computational region in the map display. It's such a
fundamental part of how GRASS works...


  +1

Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-12-24 Thread Micha Silver

  
  

On 24/12/2018 14:01, Martin Landa
  wrote:


  Hi,

st 26. 9. 2018 v 20:27 odesílatel Anna Petrášová  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)?




I'd like to see the region displayed by default. Usually the
  first thing I do is show the computational region in the map
  display. It's such a fundamental part of how GRASS works...



  
Ma

[1] https://trac.osgeo.org/grass/ticket/3519



-- 
Micha Silver
Ben Gurion Univ.
Sde Boker, Remote Sensing Lab
+972-523-665918
  

___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-12-24 Thread Martin Landa
Hi,

st 26. 9. 2018 v 20:27 odesílatel Anna Petrášová  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
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-09-26 Thread Huidae Cho
Ok, so blue means the current display is the full computational region
(OK). Red means the current display is a subset of the region (zoomed in,
OK). What about when you zoom out and the display contains and is bigger
than the computational region? It is still red. Not blue even if you are
seeing the full region. The last case confuses me. When is it red or blue?

Thanks,
Huidae
-- 
Huidae Cho, Ph.D., P.E. (MD), M.ASCE, CFM, GISP
https://idea.isnew.info
Sent from my phone

On Wed, Sep 26, 2018, 2:27 PM Anna Petrášová  wrote:

>
>
> On Wed, Sep 26, 2018 at 1:50 PM Huidae Cho  wrote:
>
>> This is a great feature, but I was wondering why it turns red on zoom
>> in/out.
>>
>>
> 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?
>
> Anna
>
> On Tue, Sep 25, 2018 at 4:32 PM Markus Neteler  wrote:
>>
>>> On Tue, Sep 25, 2018 at 10:28 PM Veronica Andreo 
>>> wrote:
>>> >
>>> > That's the computational region limits which are now visible by
>>> default in Map display and wx monitors.
>>> > However, I agree that an option to make it invisible as before would
>>> make sense.
>>>
>>> Just disable it at left bottom of the display window -> the trick is
>>> that you need to *first* switch to "Show comp. extent" which isn't obvious:
>>>
>>> [image: image.png]
>>>
>>> > You can open a ticket for this
>>>
>>> Not needed :)
>>>
>>> But I think that the "Show computational extent" should always be there.
>>> Maybe a ticket for that wish?
>>>
>>
>>
>> +1
>>
>>
>>
>>> Markus
>>>
>>> PS: sorry for HTML email
>>> ___
>>> grass-user mailing list
>>> grass-user@lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/grass-user
>>
>>
>>
>> --
>> Huidae Cho, Ph.D., PE, M.ASCE, CFM, GISP
>> Open Source GIS Developer, GRASS GIS Development Team
>> ___
>> grass-user mailing list
>> grass-user@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-user
>
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-09-26 Thread Anna Petrášová
On Wed, Sep 26, 2018 at 1:50 PM Huidae Cho  wrote:

> This is a great feature, but I was wondering why it turns red on zoom
> in/out.
>
>
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?

Anna

On Tue, Sep 25, 2018 at 4:32 PM Markus Neteler  wrote:
>
>> On Tue, Sep 25, 2018 at 10:28 PM Veronica Andreo 
>> wrote:
>> >
>> > That's the computational region limits which are now visible by default
>> in Map display and wx monitors.
>> > However, I agree that an option to make it invisible as before would
>> make sense.
>>
>> Just disable it at left bottom of the display window -> the trick is that
>> you need to *first* switch to "Show comp. extent" which isn't obvious:
>>
>> [image: image.png]
>>
>> > You can open a ticket for this
>>
>> Not needed :)
>>
>> But I think that the "Show computational extent" should always be there.
>> Maybe a ticket for that wish?
>>
>
>
> +1
>
>
>
>> Markus
>>
>> PS: sorry for HTML email
>> ___
>> grass-user mailing list
>> grass-user@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-user
>
>
>
> --
> Huidae Cho, Ph.D., PE, M.ASCE, CFM, GISP
> Open Source GIS Developer, GRASS GIS Development Team
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-09-26 Thread Huidae Cho
This is a great feature, but I was wondering why it turns red on zoom
in/out.

On Tue, Sep 25, 2018 at 4:32 PM Markus Neteler  wrote:

> On Tue, Sep 25, 2018 at 10:28 PM Veronica Andreo 
> wrote:
> >
> > That's the computational region limits which are now visible by default
> in Map display and wx monitors.
> > However, I agree that an option to make it invisible as before would
> make sense.
>
> Just disable it at left bottom of the display window -> the trick is that
> you need to *first* switch to "Show comp. extent" which isn't obvious:
>
> [image: image.png]
>
> > You can open a ticket for this
>
> Not needed :)
>
> But I think that the "Show computational extent" should always be there.
> Maybe a ticket for that wish?
>


+1



> Markus
>
> PS: sorry for HTML email
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user



-- 
Huidae Cho, Ph.D., PE, M.ASCE, CFM, GISP
Open Source GIS Developer, GRASS GIS Development Team
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-09-25 Thread Rich Shepard

On Tue, 25 Sep 2018, Markus Neteler wrote:


Just disable it at left bottom of the display window -> the trick is that
you need to *first* switch to "Show comp. extent" which isn't obvious:


  Well, that is certainly well hidden. :-)


But I think that the "Show computational extent" should always be there.
Maybe a ticket for that wish?


  +1!

Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-09-25 Thread Veronica Andreo
El mar., 25 sept. 2018 a las 22:32, Markus Neteler ()
escribió:

> On Tue, Sep 25, 2018 at 10:28 PM Veronica Andreo 
> wrote:
> >
> > That's the computational region limits which are now visible by default
> in Map display and wx monitors.
> > However, I agree that an option to make it invisible as before would
> make sense.
>
> Just disable it at left bottom of the display window -> the trick is that
> you need to *first* switch to "Show comp. extent" which isn't obvious:
>
> [image: image.png]
>

:D I completely missed that one! This is actually the very first time I
inspect that dropdown menu... ops


> > You can open a ticket for this
>
> Not needed :)
>
> But I think that the "Show computational extent" should always be there.
> Maybe a ticket for that wish?
>

> Markus
>
> PS: sorry for HTML email
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-09-25 Thread Markus Neteler
On Tue, Sep 25, 2018 at 10:28 PM Veronica Andreo 
wrote:
>
> That's the computational region limits which are now visible by default
in Map display and wx monitors.
> However, I agree that an option to make it invisible as before would make
sense.

Just disable it at left bottom of the display window -> the trick is that
you need to *first* switch to "Show comp. extent" which isn't obvious:

[image: image.png]

> You can open a ticket for this

Not needed :)

But I think that the "Show computational extent" should always be there.
Maybe a ticket for that wish?

Markus

PS: sorry for HTML email
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-09-25 Thread Veronica Andreo
That's the computational region limits which are now visible by default in
Map display and wx monitors.
However, I agree that an option to make it invisible as before would make
sense.
You can open a ticket for this

Vero

El mar., 25 sep. 2018 14:24, Rich Shepard 
escribió:

> On Tue, 25 Sep 2018, Rich Shepard wrote:
>
> > Just built the latest release from 7.7.svn (I think it's 73396) and when
> I
> > run 'd.mon start=wx0' I see a vertical rectangle with a blue border in
> the
> > center (see attached screenshot.png). d.erase does nothing to it and
> > trying to print it as content fails; there's nothing to print.
>
>Just for grins, I started grass7.7.svn with the GUI. Now the
> blue-bordered
> rectangle fills the map display window top-to-bottom and almost completely
> side-to-side.
>
> Rich
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-09-25 Thread Rich Shepard

On Tue, 25 Sep 2018, Rich Shepard wrote:


Just built the latest release from 7.7.svn (I think it's 73396) and when I
run 'd.mon start=wx0' I see a vertical rectangle with a blue border in the
center (see attached screenshot.png). d.erase does nothing to it and
trying to print it as content fails; there's nothing to print.


  Just for grins, I started grass7.7.svn with the GUI. Now the blue-bordered
rectangle fills the map display window top-to-bottom and almost completely
side-to-side.

Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

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

2018-09-25 Thread Rich Shepard

  Just built the latest release from 7.7.svn (I think it's 73396) and when I
run 'd.mon start=wx0' I see a vertical rectangle with a blue border in the
center (see attached screenshot.png). d.erase does nothing to it and trying
to print it as content fails; there's nothing to print.

  Any ideas on where this originates and how to remove it?

Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user