Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AppPosition config.xml AppPosition tag cloud sync issues #2289

Closed
mcduck76 opened this issue Sep 16, 2016 · 2 comments
Closed

AppPosition config.xml AppPosition tag cloud sync issues #2289

mcduck76 opened this issue Sep 16, 2016 · 2 comments

Comments

@mcduck76
Copy link

Description of the Issue

Syncing the config.xml file over a cloud service potentially leads to serious issues with the AppPosition tag. For example, saving the config.xml file from a PC with a high resolution screen and then loading it from a PC with a regular resolution screen produces a huge main window (or plain renders the main window off screen).
The same issue occurs with the positioning if the config file is saved and then loaded from setups with a different number of attached monitors.

Fix proposal no 1

  1. When saving the AppPosition attributes, account for the screen dpi (using the existing DPIManager class to scaleX/Y).
  2. When loading the AppPosition attributes perform the opposite conversion.
  3. When loading the AppPosition attributes, check that the window position being loaded is visible in the current setup (if not, use default size/position).

Fix proposal no 2

When cloud syncing is enabled, do not persist the AppPosition in config.xml.

@mcduck76 mcduck76 changed the title AppPosition config.xml tag cloud sync issues AppPosition config.xml AppPosition tag cloud sync issues Sep 16, 2016
@u01jmg3
Copy link

u01jmg3 commented Feb 14, 2017

Duplicate of #1121 but good idea

@MetaChuh
Copy link

MetaChuh commented May 1, 2019

many thanks for your cloud sync ideas.

please do the following, if you have 2 or more machines, where you would like to backup your settings e.g. to dropbox or onedrive, without syncing the recent file list or windows position to the other machine:

(note: we do not have any information about your setup, so we can only provide an example, using onedrive, one notebook and one stationary pc)

  • open your OneDrive folder.
  • create one folder called e.g. Notepad++ PC and one folder called e.g. Notepad++ NoteBook.
  • go to both machines, open up notepad++ and go to settings > preferences > cloud.
  • on the stationary pc set your cloud location path to Notepad++ PC.
  • on the notebook set your cloud location path to Notepad++ NoteBook.
  • close notepad++ on both machines for the changes to take effect.

after that, both notepad++ installs will not use the recent file list, or the last window position of the respective other install, but you will still have your settings backed up and reachable as files for comparison at both machines.

there is currently no need to change the behaviour of the cloud feature, as it works as designed.

thank you for your help and best regards.

@MetaChuh MetaChuh closed this as completed May 1, 2019
donho pushed a commit that referenced this issue Dec 26, 2023
Scintilla 5.4.1
https://www.scintilla.org/scintilla541.zip
Released 27 December 2023.

1.  Add IDocumentEditable interface to allow efficient interaction with document objects which may not be visible in a Scintilla instance. This feature is provisonal and may change before being declared stable. For better type-safety, the ScintillaCall C++ API uses IDocumentEditable* where void* was used before which may require changes to client code that uses document pointer APIs DocPointer, SetDocPointer, CreateDocument, AddRefDocument, and ReleaseDocument.
2.  Ctrl-click on a selection deselects it in multiple selection mode.
3.  Add SCI_SELECTIONFROMPOINT for modifying multiple selections.
4.  Add SCI_SETMOVEEXTENDSSELECTION and SCI_CHANGESELECTIONMODE to simplify selection mode manipulation.
5.  Improve performance of global replace by reducing cache invalidation overhead. [Feature #1502](https://sourceforge.net/p/scintilla/feature-requests/1502/).
6.  Fix regular expression search for "\<" matching beginning of search when not beginning of word and for "\>" not matching line end. [Bug #2157](https://sourceforge.net/p/scintilla/bugs/2157/).
7.  Fix regular expression search failure when search for "\<" followed by search for "\>". [Bug #2413](https://sourceforge.net/p/scintilla/bugs/2413/).
8.  Fix regular expression assertion (^, $, \b. \B) failures when using SCFIND_CXX11REGEX. [Bug #2405](https://sourceforge.net/p/scintilla/bugs/2405/).
9.  Fix regular expression bug in reverse direction where shortened match returned. [Bug #2405](https://sourceforge.net/p/scintilla/bugs/2405/).
10. Avoid character fragments in regular expression search results. [Bug #2405](https://sourceforge.net/p/scintilla/bugs/2405/).
11. With a document that does not have the SC_DOCUMENTOPTION_TEXT_LARGE option set, allocating more than 2G (calling SCI_ALLOCATE or similar) will now fail with SC_STATUS_FAILURE.
12. Protect SCI_REPLACETARGET, SCI_REPLACETARGETMINIMAL, and SCI_REPLACETARGETRE from application changing target in notification handlers. [Bug #2289](https://sourceforge.net/p/scintilla/bugs/2289/).

Lexilla 5.3.0
https://www.scintilla.org/lexilla530.zip
Released 27 December 2023.

1. Fix calling AddStaticLexerModule by defining as C++ instead of C which matches header. [Bug #2421](https://sourceforge.net/p/scintilla/bugs/2421/).
2. Bash: Fix shift operator << incorrectly recognized as here-doc. [Issue #215](ScintillaOrg/lexilla#215).
3. Bash: Fix termination of '${' with first unquoted '}' instead of nesting. [Issue #216](ScintillaOrg/lexilla#216).
4. HTML: JavaScript double-quoted strings may escape line end with '\'. [Issue #214](ScintillaOrg/lexilla#214).
5. Lua: recognize --- doc comments. Defined by [LDoc](https://github.com/lunarmodules/ldoc). Does not recognize --[[-- doc comments which seem less common.

Close #14375
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants