# Perspective - binding to current breakpoint value

**URL:** <https://forum.inductiveautomation.com/t/perspective-binding-to-current-breakpoint-value/26180>\
**Category:** Ignition Early Access\
**Created:** [June 29, 2019, 11:54am UTC](https://forum.inductiveautomation.com/t/perspective-binding-to-current-breakpoint-value/26180 "2019-06-29T11:54:51Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [July 1, 2019, 7:52pm UTC](https://forum.inductiveautomation.com/t/perspective-binding-to-current-breakpoint-value/26180/6 "2019-07-01T19:52:36Z")

</div>

As we previously mentioned in this thread, providing insight into Breakpoint properties is inherently dangerous as it invites (pseudo-code)

```auto
self.page.breakPointInUse = self.view.props.breakpoints[indexIWant]

```

when really it’s not on the View or code to determine which breakpoint is in use; that should fall entirely on the backend code.

Viewport dimensions on the other hand are absolutely something a user might like to know about. Whether we should allow for writing back to them is something else entirely, so in what way do we provide those values? They’re independent to the session, so session properties seems the logical choice, but if they’re read-only we need to lock them down, which is something we need to look into.

---

_[View the full topic](https://forum.inductiveautomation.com/t/perspective-binding-to-current-breakpoint-value/26180)._