# '\[Feature Request\]' Fix a component to a location **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [February 7, 2025, 6:32pm UTC](https://forum.inductiveautomation.com/t/feature-request-fix-a-component-to-a-location/102049 "2025-02-07T18:32:38Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\ **Post date:** [February 7, 2025, 8:37pm UTC](https://forum.inductiveautomation.com/t/feature-request-fix-a-component-to-a-location/102049/6 "2025-02-07T20:37:32Z")
Yes, you can lock items in Perspective Designer. See this post to make items ignore clicks/drags/selection: > [@\[BUG\]CSS Pointer-Events : None](https://forum.inductiveautomation.com/t/bug-css-pointer-events-none/73034): > > I don't know if this is a bug that IA can fix or not, but when the property "Pointer-Events : none" is applied to a component, it can no longer be clicked on in the designer - you have to locate it in the project browser or use the click-drag/highlight area to select it. I want operators to be able to click through the component in a session, but I would still like to be able to select the component within the designer. As a workaround I've created a custom prop at the root level for the view … If you want to automatically switch this to accept interaction at runtime while locking in Designer, see my reply to the post: > [@\[BUG\]CSS Pointer-Events : None](https://forum.inductiveautomation.com/t/bug-css-pointer-events-none/73034/2): > > You can automate the switching with a binding like this: Note switching via binding is affected by the following Ignition bug which can cause it to see the Designer as a client until Designer restart: > [@\[IGN-6238\] Designer session type changes from designer to browser](https://forum.inductiveautomation.com/t/ign-6238-designer-session-type-changes-from-designer-to-browser/60867): > > This session property that begins as designer when Designer is first opened changes to browser at some point. [image] It may have to do with connection loss and reconnect between Designer and Gateway. I noticed this when scripting startup actions to hide components EXCEPT in Designer where we want to see them for configuration. When this session property changes incorrectly to browser, closing Designer and reopening gets us back to correct designer property. Interestingly the gateway Perspect… --- _[View the full topic](https://forum.inductiveautomation.com/t/feature-request-fix-a-component-to-a-location/102049)._