# Option to focus app preview window on Submile text save

**URL:** <https://forums.fusetools.com/t/option-to-focus-app-preview-window-on-submile-text-save/1212>\
**Category:** Feature Suggestions\
**Created:** [November 12, 2015, 6:20am UTC](https://forums.fusetools.com/t/option-to-focus-app-preview-window-on-submile-text-save/1212 "2015-11-12T06:20:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Peter\_Janett](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/peter_janett/32/479_2.png) [@Peter\_Janett](https://forums.fusetools.com/u/Peter_Janett)\
**Post date:** [November 12, 2015, 6:20am UTC](https://forums.fusetools.com/t/option-to-focus-app-preview-window-on-submile-text-save/1212/1 "2015-11-12T06:20:28Z")

</div>

When comparing Fuse to Appcelerator and others, the real time changes are what really seperates Fuse from the others, at least in my opinion. 🙂

I’ve been working on parts of my app that require me to click the screen, and while I LOVE the fact that the preview window auto reloads on save, it’d love it even more if the preview app focused on save.

This may seem a bit trivial, but if you are working on something you don’t see until you click on something within the app, then every time you go to view your changes, you first have to click the preview window to put it in focue, then click again to actually click the action within the app you are editing.

It’s a little thing, but would add even more polish to the real time advantage of Fuse.

Thanks,

Peter Janett

New Media One Web Services [http://www.NewMediaOne.net](http://www.NewMediaOne.net) [http://GeoDigs.com](http://GeoDigs.com) support “at” [newmediaone.net](http://newmediaone.net) (303)828-9882

Add us to your address book: [http://www.newmediaone.net/New\_Media\_One.vcf](http://www.newmediaone.net/New_Media_One.vcf)

---

<div class="post-metadata">

**Author:** ![Anders\_Lassen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/anders_lassen/32/522_2.png) [@Anders\_Lassen](https://forums.fusetools.com/u/Anders_Lassen)\
**Post date:** [November 16, 2015, 10:22pm UTC](https://forums.fusetools.com/t/option-to-focus-app-preview-window-on-submile-text-save/1212/2 "2015-11-16T22:22:45Z")

</div>

Hi Peter,

Thanks for the feedback. This request has been noted, but I believe this is a matter of taste, so if we add it it will probably be as an option, not the standard.

However, as a teaser, we are planning to add peristent states between refresh. This means Fuse will keep the app in the same logical state between recompiles of UX/JS 🙂

---

<div class="post-metadata">

**Author:** ![Anders\_Lassen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/anders_lassen/32/522_2.png) [@Anders\_Lassen](https://forums.fusetools.com/u/Anders_Lassen)\
**Post date:** [November 16, 2015, 10:24pm UTC](https://forums.fusetools.com/t/option-to-focus-app-preview-window-on-submile-text-save/1212/3 "2015-11-16T22:24:52Z")

</div>

Hi Peter,

Thanks for the feedback. This request has been noted, but I believe this is a matter of taste, so if we add it it will probably be as an option, not the standard.

However, as a teaser, we are planning to add peristent states between refresh. This means Fuse will keep the app in the same logical state between recompiles of UX/JS 🙂 This largely addresses the same issue.

---

<div class="post-metadata">

**Author:** ![Anders\_Lassen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/anders_lassen/32/522_2.png) [@Anders\_Lassen](https://forums.fusetools.com/u/Anders_Lassen)\
**Post date:** [November 16, 2015, 10:33pm UTC](https://forums.fusetools.com/t/option-to-focus-app-preview-window-on-submile-text-save/1212/4 "2015-11-16T22:33:07Z")

</div>

Hi Peter,

Thanks for the feedback. This request has been noted, but I believe this is a matter of taste, so if we add it it will probably be as an option, not the standard.

However, as a teaser, we are planning to add peristent states between refresh. This means Fuse will keep the app in the same logical state between recompiles of UX/JS 🙂 This largely addresses the same issue.