add .bounds_ method to Stethoscope

[prko]

Purpose and Motivation

This is a reopened PR: #6230
This PR

• allows you to set the size and position of Stethoscope,
  • e.g. s.scope.bounds_(Rect(100, 200, 300, 100))
• and change the window resizing behaviour.

demo video:
https://www.dropbox.com/scl/fi/26952qepzu3iczj9bi0cq/s.bounds_-behaviour.mov?rlkey=suub8zyf6ujpksc7ugieggp02&dl=0

Types of changes

• Documentation
• New feature

To-do list

• Code is tested
• All tests are passing
• Updated documentation
• This PR is ready for review

[prko]

Please let me know if this PR should be split again as follows:

• add .bounds_ method to s.scope
• Change resizing behaviour

[mtmccrea]

I'm in favor of adding the bounds_ method to Stethoscope, but not making modifications of the requested size based on screen bounds.

The reason is that we found previously that setting geometry based on Window.screenBounds can have unpredictable results when using multiple monitors (a bug you helped uncover, thanks ;)). And in general the user may have a reason for setting bounds in unusual ways, and can handle limiting to screen bounds themselves if they'd like. Open to other opinions on this though.

Please let me know if this PR should be split again as follows:
add .bounds_ method to s.scope
Change resizing behaviour

So given there may be split views on this, the resizing behavior change could delay the other change you want to make

[prko]

Done!

Now I see the benefit of following your and @jrsurge's advice! This PR is also the best for me, as I know at a glance what I have done here!

[mtmccrea]

Please add documentation for the added method.

Note for the description of the argument that:
rect can be a Rect or anything that responds to .asRect.

For example the scope bounds can be set with:

s.scope.bounds_(Rect(100, 200, 500, 600));
s.scope.bounds_([100, 200, 500, 600]);
s.scope.bounds_(Size(500, 600));

[prko]

@mtmccrea

Please add documentation for the added method.

Done!

Thanks for the instructions, and sorry for my clumsy process. A few days ago, I merged by clicking update on each of the outdated branches... So the histories are very dirty. In the future, I will do what you wrote on the wiki.

[telephon]

an object with a setter should also have a getter.

[mtmccrea]

UsingPoint perhaps isn't the best example since, although that's valid, specifying a Point implicitly sets the position to [0,0]. I think omitting an example in the arg description is ok, since you provide examples below anyway.

Something like:

A link::Classes/Rect::, or any object responding to the link::Search#-asRect:: method.

(suggestion untested in the renderer)

As an aside I think Point:-asRect is rather counterintuitive (a point is a position) compared to, say, Size:-asRect.

[prko]

have done!
39802c6

[mtmccrea]

an object with a setter should also have a getter.

Good point! I noticed the method documentation listed a return value, though there isn't yet actually a getter method.

[prko]

@telephon @mtmccrea

an object with a setter should also have a getter.
Good point! I noticed the method documentation listed a return value, though there isn't yet actually a getter method.

I thought about it too! Thank you very much. I have done that.
I also added a message if the width of a Rect is less than the minimum value of 264:
7ea3085

[prko]

@mtmccrea thanks!!!