I am using eM Client 3.5 and was wondering, as a new user, if it is possible to make the reading pane a fixed width as, at the moment, when I shut down the app and the restart it, the readin pane takes up most of the screen in pushing the email list window over the left more…
When you refer to ‘reading panel’ do you mean the e-mail preview below the subject (by default) or a new window by double-click the mail subject? Either all you can resize both of them and eM Client will be able to remember them.
Hi Filip, don’t know if it related, though I don’t have problem eM saving panel size state, but I do have problem eM memorizing local folder being minimized as mentioned here: https://discourse.emclient.com/emclient/to…
Also with my other problem: https://discourse.emclient.com/emclient/to… though it fixed in version 3.0 with .NET2 SP2, but eM 3.5 seems behave oddly as sometimes if I go over the e-mails too faster, it will not get marked automatically.
Thanks for the data. So far we were unable to reproduce it. With your configuration eM Client started maximized and the reading pane had a reasonable width. If the application was restored (by using the button in title bar) then the splitter between reading pane and the message list stayed at the same absolute position and the reading pane became really small.
Does eM Client start with a maximized window for you?
Are you running it using the shortcut in the Start Menu or through some other way?
Are you using multi-monitor setup?
I am using 3 monitors and normally launch the applcation from an app called rocket dock (http://rocketdock.com/)). From their it launches maximised on one of the monitors.
If I launch from the start bar, it also launches maximised and the same occurs in that the window resizes to a default.
I saved all the files in the \AppData\Roaming\eM Client\ folder, uninstalled completely the 3.5 version, installed 3.0 , then added the settings files I saved and tried to restart the application but it said that the database was from a later version…
Looks like the database isn’t backward compatible. The path is correct for database. You may delete the database just to check if 3.0 has the same problem.