Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Tue, 23 Apr 2024 20:48:33 +0000
Suggested Solution > Window Size and Position Not Restored
View Count: 2785
| [2015-07-30 07:44:05] |
| User51760 - Posts: 108 |
|
As some other users I had difficulties with windows size and position not restored as described in Sierra Chart Help Topic 14 http://www.sierrachart.com/index.php?l=doc/helpdetails14.html DEFINITELY this behaviour is not a problem of Sierra Chart, but it sometimes shows in SC using a multimonitor system that is not properly set up. Having done a lot of research with Microsoft, Nvidia, AMD and the manufacturers – with no success: All those companies claim no responsibility for malfunction of GetWindowPlacement and SetWindowPlacement. By trial and error I could solve the problem for a 6 monitor system by following the steps below: A.) First problem solving step: Teach Windows OS to remember the last size and position of program windows: 1. Move a window to its desired monitor. 2. Grab a corner of the window and resize the window to just half an inch space to the monitor edges on all sides. 3. Minimize the window via the minimize button on the upper right edge of the window. 4. Click the window icon in the taskbar and bring up the window again. 5. Repeat this minimizing-resizing 3 or 4 times. 6. Exit the program with “Saving All”. 7. Run the program again and open the window in question. If Windows OS brings up the window on the desired monitor in the desired size and position repeat the process for each and every window. 8. If this solution does not help (means: If the window is again repositioned to a default location on the main monitor) try the next solution: B.) Second problem solving step: certain combinations of Windows OS (especially Windows 7) and 2 or more AMD graphics cards from certain manufacturers need very careful setup of the multimonitor system. Windows OS needs to be taught to recognize and remember the monitors AND the last size and position of your windows. 1. 1.1 Do not use Crossfire technology with AMD graphics cards nor SLI with Nvidia graphics cards. 1.2 Make sure to use ACTIVE Adapters if connecting graphics card DisplayPort connector to HDMI/DVI/VGA connector of monitor. 1.3 Only connect 3 or less monitors to each graphics card, even having more than 3 connectors. 2. Starting with the graphics card closest to the mainboard (in most cases the most upper graphics card) connect the most recent (means: technically the most modern) connector to the physically first monitor and keep this order of most recent (most modern) connectors: newest ----------------------------> oldest DisplayPort > HDMI > DVI-I > DVI-D > VGA (D-Sub). Refer to the attached illustration. 3. Give Windows OS some time to recognize and remember the first monitor: wait a minute. 4. After having connected the first monitor and some flickering of the monitor use Rightclick in free Desktop space > screenresolution and bring up the screenresolution control panel. Check if the monitor is correctly recognized. 5. Close Control Panel. 6. Connect the physically second monitor to the next most recent (second most modern) connector. 7. Give Windows some time to recognize and remember the second monitor. 8. Having connected the second monitor and some flickering of the monitors use Rightclick in free Desktop space > screenresolution and bring up the screenresolution control panel. Check if both monitors are correctly recognized. 9. Repeat this procedure for each of your monitors. 10. Start connecting the second graphics card with the most recent connector as you did with the first graphics card (refer to the attached illustration). 11. After having connected all monitors to all graphiccards restart your computer with all monitors turned ON. 12. Check if Windows OS has recognized all monitors in the correct order through Rightclick in free Desktop space > screenresolution and bring up the screenresolution control panel. 13. Always start your system with all monitors already turned ON. 14. Good luck, Best, Chris |
 graphics_connectors_win7.png / V - Attached On 2015-07-30 07:40:09 UTC - Size: 446.33 KB - 478 views |
| [2018-01-30 15:33:15] |
| patrader - Posts: 92 |
|
I just ran into the same problem and have a low-tech solution that worked for me. I'm running multiple monitors and my charting and DOM windows were/are not attached. The problem came out of nowhere. One work-space I had set up was remembering the position and size of my windows. The other newer work-space was not. The difference between the two was HOW I had sized the windows. The problem was the windows SNAP function. In the second work-space I was using SNAP to size four windows to each quarter of the screen (then dragging the edges to get the windows exactly where I wanted them). Every re-start would result in the windows reverting back to their pre-SNAP size and position. SOLUTION: I put the windows I wanted onto each screen then right clicked the windows task bar and chose "Show Windows stacked" and from there I manually dragged the outer edges left-right or up-down to get the windows exactly where I wanted them. Re-started SC and it remembered the position placement/sizes. BOTTOM LINE: Either 100% manually sizing windows, or manually sizing them after using Show Windows stack = fine. Using SNAP = not fine. |
| [2018-01-30 18:23:00] |
| |
|
In response to post #2 most probably the functionality that is not causing the window positions and sizes to be saved is a deliberate decision by Microsoft.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-01-30 18:23:12
|
To post a message in this thread, you need to log in with your Sierra Chart account: