feat(desktop): save and restore window state

[ni00]

PR Checklist

What is the current behavior?

Won't save and restore window position and size.

Issue Number

#1849

What is the new behavior?

Save and restore window position and size.

Does this PR introduce a breaking change?

• Yes
• No

Specific Instructions

Other information

reference: electron/electron#526

[ysfscream]

So many thanks for implementing the window state persistence feature!

The implementation looks thoughtful and handles the multi-monitor scenario well. Here are some thoughts that might be helpful:

1. We might want to consider adding maximized state handling?

// Example approach:
electronStore.set('windowState', {
  bounds: win.getBounds(),
  isMaximized: win.isMaximized()
})

2. Would it make sense to add some error handling? Something like:

try {
  win.setBounds(savedBounds)
} catch (error) {
  // log some error here
  console.error('Failed to restore window bounds:', error)
  // Handle fallback
}

3. Can we sync the latest window size values to the database for better persistence?

Only when we open it for the first time do we use 1025 * 749 as the default value?

const defaultBounds = {
  width: 1024,
  height: 768,
  x: 0,
  y: 0
}

[ni00]

I'm considering removing the height and width fields from SettingEntity

Reasons:

1. These two fields currently only provide default values and cannot be explicitly modified, which is inconsistent with other configurable properties in SettingEntity that can be adjusted in the settings page

2. Window size, position, and other state properties are better suited for internal application state management, and don't need to be included in user-configurable settings

3. Following practices from other Electron applications, window states are typically managed using lightweight storage solutions like electron-store, rather than being written to the main database that requires backup

4. These window state properties are not noticeable to users and don't need to be synchronized in backups

[Red-Asuka]

@ni00 Thank you very much for your contribution to the project! I have optimized the existing code and resolved the building error. I completely agree with your views on storing window width and height data. In version v1.x, we will no longer use the width and height from the database table. These have already been removed in version v2.x. For more details on the changes, please see: #1868

[ysfscream]

Thanks to all @ni00 @Red-Asuka