Stop window size from saving to the cloud

Lycan Thrope

@PeterJones ,
I was going to respond to him, a possible fix and then I saw your response pop up. Agreed, I had also thought about people using the cloud settings for different machines, but most likely didn’t give a hoot about the inconvenience of resizing or maximizing the window.

If he wants different config.xml files for each machine, it would seem to be, that creating a separate directory on GoogleDrive, and a corresponding directory on his local GoogleDrive and pointing each machine to their GoogleDrive local directory each pointing to a diffent directory with the saved settings on GoogleDrive, would solve his problem, but that would take initiative on his part to do that, rather than assuming a developer should have read his mind and implemented it for his convenience. This from someone that doesn’t use multiple machines (yet) with cloud settings saving needs.

PeterJones

@superluig164 said in Stop window size from saving to the cloud:

And again, it doesn’t sync plugins, so clearly there was some thought that certain things can’t be properly synced between installs, right?

It doesn’t sync plugins, because the plugins aren’t ever stored in AppData, and the Cloud settings are meant to store certain settings that would normally be in AppData in the Cloud instead. And it apparently doesn’t store plugin settings, either, despite them being stored in the AppData folder; I personally have expressed my opinion to the Developer that the plugin settings should be part of what’s put in the Cloud folder, but he disagrees.

thought that certain things can’t be properly synced

And those are kept in separate files. Trying to separate out different settings that are all stored in the same config.xml would be impractical, so the settings that aren’t sync’d would have to be separated out into a different file from the ones that are synced. And, once again, I don’t agree that there’s as clear a separation of the two as you have in your mind.

And it’s my guess that the Developer will not choose to pick-and-choose to extract some settings that have been in config.xml for time-immemorial to suddenly be in some separate file all of a sudden, without a really good reason (and I am doubtful that your current Issue description would be convincing enough, though I’ve been wrong about my guesses of the Developer’s actions before, and will be again).

PeterJones

@Lycan-Thrope said in Stop window size from saving to the cloud:

If he wants different config.xml files for each machine,

But that’s not what he wants – or, not fully. To me, it’s obvious wants most of his settings the same between the different machines, but he just doesn’t think that window size should be part of those synced settings.

Lycan Thrope

@PeterJones ,
What I read that he wants, is for him to just save his settings to GoogleDrive, and be able to use it for two machines, with the program having the mind reading ability to differentiate which one is using it. Basically, he wants the app to change for his needs, rather than trying to find a way to implement what he wants without making the app change.

Would that be an erroneous read?

Edit: I agree with what you post above, but like this conversation, what one reads, is sometimes dependent on someone’s view. Which is why we discuss things and hash it out, until both parties are understanding the root issue. :-) Or a possible solution.

PeterJones

@Lycan-Thrope said in Stop window size from saving to the cloud:

Would that be an erroneous read?

I think it’s an unfair rephrasing of what he said. I stand by my summary sentence.

Basically, he wants the app to change for his needs,

When you boil it down, that’s what all feature requests are.

I don’t fault him for his request, or for wanting Notepad++ to cater to him – we all do, to some extent or another. I just don’t think he’s going to be given what he wants, and I’m not convinced that the implementation he envisions will be as practical or as universally-accepted as he seems to think it will.

Lycan Thrope

@PeterJones ,
Agreed, although I did give him several chances to understand what I was getting at, before I became unfair. :-) As a goup, we also gave him several ways to accomplish the goal, but he was rebuffing those for the app change option.

Lycan Thrope

@PeterJones ,
I think I’m going to go try my suggestion, using the Standard install and a portable install and save both to GoogleDrive in different directories on the GoogleDrive cloud.

Lycan Thrope

@Lycan-Thrope , @superluig164 , @PeterJones
Indeed, my suggestion does work.

I hate using Cloud stuff, but for the sake of testing, I used my GoogleDrive, setup two identical directories on the GoogleDrive Cloud side, and also in my Desktop GoogleDrive syncing drive.

I then enabled and then pointed my Standard Install NPP to the local GoogleDrive directory and did the same with the portable install pointing to the Portable directory on the GoogleDrive local directory.

I closed both and restarted them, and then left the portable install editor window not maximized, and sitting in the lower right corner of the screen, and the Standard install full screen maximized.

My GoogleDrive saved settings were as such:
Portable:

<GUIConfig name="AppPosition" x="502" y="153" width="1100" height="700" isMaximized="no" />

Standard:

<GUIConfig name="AppPosition" x="3" y="4" width="725" height="700" isMaximized="yes" />

So, as you see, the concept works, and since you are a GoogleDrive user @superluig164 , the solution is very simple for someone adept at using their GoogleDrive to solve such a thorny issue.

Now I don’t like using Cloud syncing, because I back up my drive stuff, and I hate the slow and sometimes problematic issues that using a Cloud drive presents. For instance, my UDL was already installed in each version. Enabling the Cloud directory forced me to have to reinstall files that were already existing, so they could be copied to the Cloud directories. That was inconvenient, but I did it to be throrough and make sure the system worked as I was suggesting it might for proof of concept.

There is the solution that you need @superluig164 , for your multiple machine issue. No application modification needed. The application works as you wish, as long as you set up the proper Drive locations where you can separate those machine’s settings in your GoogleDrive system.

Enjoy.

Lycan Thrope

@Lycan-Thrope ,
In hindsight, and after re-reading the issue, it seems that other than the app change removing the AppPosition from the config.xml file(unlikely?), @Alan-Kilborn 's suggestion would be the best for using his GoogleDrive Cloud setup with just one config.xml for multiple machines. He has already rebuffed that, so unless he reconsiders, I guess we’ll have to wait and see if his feature request gets approved and implemented. Moving on.