Enable Zoom Options in Preferences

[nirmit]

This attempts to fix #59 by adding the option in preferences to change the zoom factor. The current available values are 80%, 100% (default), 125%, 150%, 175% and 200%.

Fixes #59

[dweremeichik]

Oh, cool! How well does it work?

[nirmit]

It works pretty well.

125%

150%

200%

[lamixer]

Fantastic! I've been waiting for this.. Thank you! Please compile a new version with this pretty soon :-)

…

On Mon, 13 Nov, 2017 at 3:38 AM, Nirmit ***@***.***> wrote: It works pretty well. 125% 150% 200% — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[dweremeichik]

@nirmit is this one ready to merge, or do you still have some changes to make?

[nirmit]

Ready to merge! Can someone test this on Linux/Windows? I don't have either. :(

[dweremeichik]

I'm 👍 on this, I will give it a spin on Linux when I get a chance.

[mikeseese]

im 👍 if @dweremeichik is

[dweremeichik]

I'll merge after testing.

[dweremeichik]

This breaks for me after opening up an email. (It resets to default).

[lamixer]

That is what happens if you set the zoom level in the config file also -- you see the zoom but clicking on something makes it revert to normal.

…

On Tue, 21 Nov, 2017 at 12:18 AM, Dylan Weremeichik ***@***.***> wrote: This breaks for me after opening up an email. (It resets to default). — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[nirmit]

Hmm... Once you set the zoom, can you check if the interfaceZoom value propagates to all the config files in ~/.nylas-mail. It seems that the old value lingers in one of the config files.

[mikeseese]

@nirmit do you have a status on this since the last comments? are you waiting on someone to test and provide feedback?

[nirmit]

@seesemichaelj the issue is that not all versions of the config.json get the updated interfaceZoom values when the user changes the default. Can you help here in making this consistent across the various config.jsons being created?

If I change the zoom options, don't click on an email from the thread list, quit Nylas, and reopen, the interfaceZoom is updated and used. The client then displays everything with the desired zoom.

[mikeseese]

Well no where in your code does it look like the config is ever being changed? Unfortunately I don't really know how to add a parameter to be written to the config file

[nirmit]

A change in settings emits a change event that triggers an atomic write. Am I missing something? In this case, the write happens in one file and not the other 9. If you change the zoom settings, you can see the changed value in one of your config.

…

On Wed, Dec 13, 2017 at 9:31 PM Mike Seese ***@***.***> wrote: Well no where in your code does it look like the config is ever being changed? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#166 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAaUJPxfpXoTB-4_EyfYVy3yxwJlIlmiks5tAIiegaJpZM4QaxzW> .

[mikeseese]

The config.json files are timestamped backups. so the one with the biggest number should be the most recent one, and the one that has your change. we always read from the most recent config file; so i wouldn't expect this to be a problem as i expect the 9 files to not have your thing as they're backed up versions of the config

[nirmit]

But the file that gets the update is not being used when a user clicks an email in the thread list. As mentioned earlier, if you quit and reopen Nylas after making the change, it persists.

…

On Wed, Dec 13, 2017 at 11:41 PM Mike Seese ***@***.***> wrote: The config.json files are timestamped backups. so the one with the biggest number should be the most recent one, and the one that has your change. we always read from the most recent config file; so i wouldn't expect this to be a problem as i expect the 9 files to not have your thing as they're backed up versions of the config — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#166 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAaUJNFkqawGiV03Z8U3uePmdDRnh-keks5tAKb5gaJpZM4QaxzW> .

[mikeseese]

Ah ok. I think you need to listen to the NylasEnv.config.onDidChange event to get the change in the config. Looks like what you're reading is just the initial config variable. Probably a similar example for this would be

nylas-mail/packages/client-app/src/browser/system-tray-manager.es6

Lines 59 to 66 in 91d6514

	this._application.config.onDidChange('core.workspace.systemTray', ({newValue}) => {
	if (newValue === false) {
	this.destroyTray();
	} else {
	this.initTray();
	}
	});
	}