Inconsistent use of terms "Border" and "Region" #97286

Open
opened 2022-04-12 19:41:39 +02:00 by ChameleonScales · 7 comments

Blender Version: 3.1.2

Short description of error
To my knowledge, the term Render Border is (or will be) deprecated. It used to be what is now called Render Region and had the same meaning. Some operators still use that term though.

Exact steps for others to reproduce the error

  • in Preferences > Interface, enable "Developer Extras"
  • in 3DView, hit F3 and type "border". There are 5 results:
    • "Zoom to Border": This one is unrelated, as it doesn't refer to Render Regions. Could still use the term Region anyway, though border is fine to me here.
    • "Reset Render Border": should definitely use the term Region
    • "Clipping Region": unrelated to Render Region, but python operator label uses "border" while the UI name uses "Region" (API backwards compatibility reasons?)
    • "Set Render Region": same here, python label uses "border", UI name uses "Region".

Keeping the legacy term in the API label makes sense (prevents add-ons from breaking), though eventually it should be consistent with the UI. At the very least the UI names should be consistent.

Note: Changing to "Region" was a great decision imo, as its meaning is much more explicit than Border.

Blender Version: 3.1.2 **Short description of error** To my knowledge, the term Render Border is (or will be) deprecated. It used to be what is now called Render Region and had the same meaning. Some operators still use that term though. **Exact steps for others to reproduce the error** - in Preferences > Interface, enable "Developer Extras" - in 3DView, hit F3 and type "border". There are 5 results: - "Zoom to Border": This one is unrelated, as it doesn't refer to Render Regions. Could still use the term Region anyway, though border is fine to me here. - "Reset Render Border": should definitely use the term Region - "Clipping Region": unrelated to Render Region, but python operator label uses "border" while the UI name uses "Region" (API backwards compatibility reasons?) - "Set Render Region": same here, python label uses "border", UI name uses "Region". Keeping the legacy term in the API label makes sense (prevents add-ons from breaking), though eventually it should be consistent with the UI. At the very least the UI names should be consistent. Note: Changing to "Region" was a great decision imo, as its meaning is much more explicit than Border.

Added subscriber: @ChameleonScales

Added subscriber: @ChameleonScales
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

Hi, thanks for the report.

"Zoom to Border": This one is unrelated, as it doesn't refer to Render Regions. Could still use the term Region anyway, though border is fine to me here.

This option is already named as Zoom Region in View > navigation popover: https://docs.blender.org/manual/en/latest/editors/3dview/navigate/navigation.html#zoom-region

Keeping the legacy term in the API label makes sense (prevents add-ons from breaking), though eventually it should be consistent with the UI

I'll leave this for #python_api & UI developers to make the decision.

Hi, thanks for the report. > "Zoom to Border": This one is unrelated, as it doesn't refer to Render Regions. Could still use the term Region anyway, though border is fine to me here. This option is already named as `Zoom Region` in View > navigation popover: https://docs.blender.org/manual/en/latest/editors/3dview/navigate/navigation.html#zoom-region > Keeping the legacy term in the API label makes sense (prevents add-ons from breaking), though eventually it should be consistent with the UI I'll leave this for #python_api & UI developers to make the decision.

This option is already named as Zoom Region in View > navigation popover:

Indeed, in fact the same operator appears twice under the 2 different names if you F3 search for "zoom".

I just realized you need to have "Developers Extras" enabled for the F3 search to show the 5 results I was previously talking about, so I added it in the steps.

> This option is already named as Zoom Region in View > navigation popover: Indeed, in fact the same operator appears twice under the 2 different names if you F3 search for "zoom". I just realized you need to have "Developers Extras" enabled for the F3 search to show the 5 results I was previously talking about, so I added it in the steps.

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

If there is doubt about what is most correct, see the dictionary:

Border:
1: A line separating two countries, administrative divisions, or other areas.
2: The edge or boundary of something, or the part near it.

Region:
1: An area, especially part of a country or the world having definable characteristics but not always fixed boundaries
2: A part of the body, especially around or near an organ.

The term 'border' is definitely incorrect, since all the the 'border' operations in Blender never refer to the borders/edged of something. For example, 'render border' doesn't only render the borders/edges, it render whatever is inside the area/region defined by the user.

'Region' is more correct.

If there is doubt about what is most correct, see the dictionary: **Border:** 1: A line separating two countries, administrative divisions, or other areas. 2: The edge or boundary of something, or the part near it. **Region:** 1: An area, especially part of a country or the world having definable characteristics but not always fixed boundaries 2: A part of the body, especially around or near an organ. The term 'border' is definitely incorrect, since all the the 'border' operations in Blender never refer to the borders/edged of something. For example, 'render border' doesn't only render the borders/edges, it render whatever is inside the area/region defined by the user. 'Region' is more correct.
Thomas Dinges added this to the 2.90 milestone 2023-02-08 16:25:00 +01:00
Philipp Oeser removed the
Interest
User Interface
label 2023-02-10 09:22:08 +01:00
Brecht Van Lommel removed this from the 2.90 milestone 2023-03-23 18:20:40 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#97286
No description provided.