# Are there options for controlling the size of the Paraview window?
**URL:** https://discourse.paraview.org/t/are-there-options-for-controlling-the-size-of-the-paraview-window/12971
**Category:** ParaView Support
**Created:** [October 2, 2023, 2:39pm UTC](https://discourse.paraview.org/t/are-there-options-for-controlling-the-size-of-the-paraview-window/12971 "2023-10-02T14:39:13Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Rob-Chase](https://discourse.paraview.org/u/Rob-Chase)
#### Post date: [October 2, 2023, 2:39pm UTC](https://discourse.paraview.org/t/are-there-options-for-controlling-the-size-of-the-paraview-window/12971/1 "2023-10-02T14:39:13Z")
I’m using Paraview python scripts to open standard exodus mesh files for interactive viewing by analysts.
Unfortunately, the user experience varies because Paraview tends to open in the same state it had at the end of the last session.
Are there Paraview command line arguments or commands in python that I can use to control the size/position, etc. of the Paraview application window? If so, are there options to ensure that specific things like the Pipeline Browser and Properties panel are visible and sized to be usable?
I’m running Paraview 5.11.1 in RHEL 7.9.
Thanks for your help.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 2, 2023, 2:47pm UTC](https://discourse.paraview.org/t/are-there-options-for-controlling-the-size-of-the-paraview-window/12971/2 "2023-10-02T14:47:37Z")
> [@Rob-Chase](#):
>
> to open in the same state it had at the end of the last session.
Wdym, same state ?
---
### Author:  [@Rob-Chase](https://discourse.paraview.org/u/Rob-Chase)
#### Post date: [October 2, 2023, 3:03pm UTC](https://discourse.paraview.org/t/are-there-options-for-controlling-the-size-of-the-paraview-window/12971/3 "2023-10-02T15:03:57Z")
The overall size and position of the Paraview window seems to be consistent with the previous session.
Also, some panels, like “Find Data” or “Color Map Editor”, may be shown if they were used in the last session.
Some users have had problems because this means that the render view is too small to effectively inspect the mesh without manually modifying the interface.
Other users have complained that the controls in the properties panel are hidden until they manually adjust the size of that panel.
Neither of these are major problems, but if they can be mitigated to save the users some time, then that would help the user experience.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 2, 2023, 3:07pm UTC](https://discourse.paraview.org/t/are-there-options-for-controlling-the-size-of-the-paraview-window/12971/4 "2023-10-02T15:07:31Z")
Well, this is an intended behavior. If a user reduced the size of the window, we (well, Qt) try to respect it.
Deleting the setting file is a way to reset to default behavior, you can also run with `--dry-run` but then no setting will ever be saved.
---
### Author:  [@Rob-Chase](https://discourse.paraview.org/u/Rob-Chase)
#### Post date: [October 2, 2023, 3:19pm UTC](https://discourse.paraview.org/t/are-there-options-for-controlling-the-size-of-the-paraview-window/12971/5 "2023-10-02T15:19:12Z")
Thanks for the prompt response.
I suspected that was the case, but I thought it was worth asking if there were any command-line or python options to override that behavior.