Niestety nie mówię po angielsku. Może ktoś polsko-angielski zainteresuje się tym i pomoże?
Odnoszę wrażenie, że ten plugin ma bardzo dyskretny błąd! Oto procedura,która go ujawnia:
1. otwórz jakikolwiek plik tekstowy (txt)
2. w dowolnym wierszu wpisz jakiś znak - marker zapali się na żółto sygnalizując zmianę
3. teraz zapisz plik - Save - marker zmienił się na zielony.
4. teraz w tym samym wierszu - WAŻNE (patrz: punkt 2!) wpisz dowolny znak - marker NIE ZMIENIA KOLORU!!! a powinien.
Ostatnią wersją, w której ten plugin działał prawidłowo była v.5.3.1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hopefully I got your point, and this is an useful feature request for Change Markers.
If a line has both saved and unsaved changes, the marker being shown is the Saved marker, which is hiding the fact that yet another change took place ever since.
Suggestions to fix: either
1/ Make the Unsaved marker prevalent over Saved; or
2/ Better: add a 3rd state, Mixed. A mixed changes line will appear in a different colour, and shall belong to both saved and unsaved history.
While I am at it, I noticed that the foreground color of a marker cannot change on the default theme, but can on alternate themes. I believe the latter doesn't really make sense, unless I am missing something?
CChris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Google translated version, for the benefit of all:
=============
Unfortunately, I do not speak English. Maybe someone interested Polish-English
and this will help?
The impression that this plugin has a very discrete error! Here is a procedure which
it reveals:
1. Open any text file (TXT)
2. in any line of a character type - a marker lights up in yellow
signal change
3. Now save the file - Save - marker changed to green.
4. Now on the same line - IMPORTANT (see point 2!), type any character --
marker does not change color! It should.
The final version, in which the plugin to work properly was the v.5.3.1
joce.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Next time, you should use Google Translate (http://translate.google.com/) too.
This way, there is a better chance your message will be answered, and less of a chance of it being deleted.
+-+-+-+-+-+-
Następnym razem, należy użyć Google Translate (http://translate.google.com/) too.
W ten sposób istnieje większe szanse wiadomość zostanie odebrane, i mniej szansę go usunąć.
joce.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
...'If a line has both saved and unsaved changes, the marker being shown is the Saved marker, which is hiding the fact that yet another change took place ever since.'...
That is slightly inaccurate. It only happens when the change takes place on the same line directly after the save. This bug and one other ( can't recall it specifically at the moment ) have both been reported in the forums ( which my search didn't find this time :/ ) and are both slated to be fixed for 5.5.
Right now I am doing much work on the developer community side of things with git and source project stuff so I haven't even taken the time to look at the code lately. But I _do_ remember that it looked like an obvious ommission on my part and just need to be fixed and tested.
Like I said... it _is_ on my todo list.
Thank you for reporting it though. It is nice to know the plugin is useful enough that people actually pay attention to those little marks. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
...'If a line has both saved and unsaved changes, the marker being shown is the Saved marker, which is hiding the fact that yet another change took place ever since.'...
That is slightly inaccurate. It only happens when the change takes place on the same line directly after the save. This bug and one other ( can't recall it specifically at the moment ) have both been reported in the forums ( which my search didn't find this time :/ ) and are both slated to be fixed for 5.5.
Right now I am doing much work on the developer community side of things with git and source project stuff so I haven't even taken the time to look at the code lately. But I _do_ remember that it looked like an obvious ommission on my part and just need to be fixed and tested.
Like I said... it _is_ on my todo list.
Thank you for reporting it though. It is nice to know the plugin is useful enough that people actually pay attention to those little marks. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A new version (essentially a complete rewrite) is in progress and will absolutely not miss changes to lines.
It will also be more stable. As some users who use N++ in particular ways (find-replace in open docs follwed by a save/save-all) have experienced stability issues.
Sincerely,
Thell
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Where to get in touch with your plugin? I had some feature requests. the colors of lines are too light for me, i want to apply my own colors, can you put some option one time.
color: rgb input or color picker!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately, change markers has been removed from the 5.5 release due to a known stability issue (when using save-all or find in open files). You can install it again easily with the plugin manager. It is currently being redeveloped to fix the issue, so hopefully it will be included again soon.
Dave.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are two known causes for this:
1/ The colours for saved and unsaved changes were chosen the same. Use the Styler Configurator to take care of this.
2/ Under some circumstances, a line with both saved and unsaved changes may show the saved marker only. When it is available, the new version of the plugin is supposed to correct this known bug.
CChris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can't access the pictures at this point, but could you elaborate?
If you have Change Markers installed, the Global styles entry in the Styler Configurator has two extra fields, Saved changes and Unsaved changes. You can adjust the background colours so that they look different. If they are different, then t may be the other issue if a line has both saved and unsaved changes, it may incorrectly show the saved marker.
CChris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have problem with Change Marker, when I have enabled this plugin and I edit file from shared folder and I wont to save documet notepad++ freeze and crash. When I diesable this plugin problem does not exist.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Niestety nie mówię po angielsku. Może ktoś polsko-angielski zainteresuje się tym i pomoże?
Odnoszę wrażenie, że ten plugin ma bardzo dyskretny błąd! Oto procedura,która go ujawnia:
1. otwórz jakikolwiek plik tekstowy (txt)
2. w dowolnym wierszu wpisz jakiś znak - marker zapali się na żółto sygnalizując zmianę
3. teraz zapisz plik - Save - marker zmienił się na zielony.
4. teraz w tym samym wierszu - WAŻNE (patrz: punkt 2!) wpisz dowolny znak - marker NIE ZMIENIA KOLORU!!! a powinien.
Ostatnią wersją, w której ten plugin działał prawidłowo była v.5.3.1
http://rapidshare.com/files/260154276/change_markers-error.jpg
radix03
Hopefully I got your point, and this is an useful feature request for Change Markers.
If a line has both saved and unsaved changes, the marker being shown is the Saved marker, which is hiding the fact that yet another change took place ever since.
Suggestions to fix: either
1/ Make the Unsaved marker prevalent over Saved; or
2/ Better: add a 3rd state, Mixed. A mixed changes line will appear in a different colour, and shall belong to both saved and unsaved history.
While I am at it, I noticed that the foreground color of a marker cannot change on the default theme, but can on alternate themes. I believe the latter doesn't really make sense, unless I am missing something?
CChris
Google translated version, for the benefit of all:
=============
Unfortunately, I do not speak English. Maybe someone interested Polish-English
and this will help?
The impression that this plugin has a very discrete error! Here is a procedure which
it reveals:
1. Open any text file (TXT)
2. in any line of a character type - a marker lights up in yellow
signal change
3. Now save the file - Save - marker changed to green.
4. Now on the same line - IMPORTANT (see point 2!), type any character --
marker does not change color! It should.
The final version, in which the plugin to work properly was the v.5.3.1
joce.
radix03,
Next time, you should use Google Translate (http://translate.google.com/) too.
This way, there is a better chance your message will be answered, and less of a chance of it being deleted.
+-+-+-+-+-+-
Następnym razem, należy użyć Google Translate (http://translate.google.com/) too.
W ten sposób istnieje większe szanse wiadomość zostanie odebrane, i mniej szansę go usunąć.
joce.
...'If a line has both saved and unsaved changes, the marker being shown is the Saved marker, which is hiding the fact that yet another change took place ever since.'...
That is slightly inaccurate. It only happens when the change takes place on the same line directly after the save. This bug and one other ( can't recall it specifically at the moment ) have both been reported in the forums ( which my search didn't find this time :/ ) and are both slated to be fixed for 5.5.
Right now I am doing much work on the developer community side of things with git and source project stuff so I haven't even taken the time to look at the code lately. But I _do_ remember that it looked like an obvious ommission on my part and just need to be fixed and tested.
Like I said... it _is_ on my todo list.
Thank you for reporting it though. It is nice to know the plugin is useful enough that people actually pay attention to those little marks. :)
...'If a line has both saved and unsaved changes, the marker being shown is the Saved marker, which is hiding the fact that yet another change took place ever since.'...
That is slightly inaccurate. It only happens when the change takes place on the same line directly after the save. This bug and one other ( can't recall it specifically at the moment ) have both been reported in the forums ( which my search didn't find this time :/ ) and are both slated to be fixed for 5.5.
Right now I am doing much work on the developer community side of things with git and source project stuff so I haven't even taken the time to look at the code lately. But I _do_ remember that it looked like an obvious ommission on my part and just need to be fixed and tested.
Like I said... it _is_ on my todo list.
Thank you for reporting it though. It is nice to know the plugin is useful enough that people actually pay attention to those little marks. :)
Just a follow up…
A new version (essentially a complete rewrite) is in progress and will absolutely not miss changes to lines.
It will also be more stable. As some users who use N++ in particular ways (find-replace in open docs follwed by a save/save-all) have experienced stability issues.
Sincerely,
Thell
Where to get in touch with your plugin? I had some feature requests. the colors of lines are too light for me, i want to apply my own colors, can you put some option one time.
color: rgb input or color picker!
Even better: Settings -> Styler Configurator, Change markers is at the bottom of the leftmost list.
CChris
And where Change Markers in version 5.5???
Unfortunately, change markers has been removed from the 5.5 release due to a known stability issue (when using save-all or find in open files). You can install it again easily with the plugin manager. It is currently being redeveloped to fix the issue, so hopefully it will be included again soon.
Dave.
Hi,
When will be release the new version of this great plugin?
The current version of the plug-in does not change color.
See photo:
: http://zapodaj.net/481d4539b822.jpg.html
: http://zapodaj.net/ae79418700d3.jpg.html
Addendum: applicable ANSI standards.
My entry number 15 is mistakenly. The problem concerns the UNICODE! Sorry for the mistake.
There are two known causes for this:
1/ The colours for saved and unsaved changes were chosen the same. Use the Styler Configurator to take care of this.
2/ Under some circumstances, a line with both saved and unsaved changes may show the saved marker only. When it is available, the new version of the plugin is supposed to correct this known bug.
CChris
"…Use the Styler Configurator to take care of this…"???
Accompanying photographs show that the style configurator is not working properly.
I can't access the pictures at this point, but could you elaborate?
If you have Change Markers installed, the Global styles entry in the Styler Configurator has two extra fields, Saved changes and Unsaved changes. You can adjust the background colours so that they look different. If they are different, then t may be the other issue if a line has both saved and unsaved changes, it may incorrectly show the saved marker.
CChris
I have problem with Change Marker, when I have enabled this plugin and I edit file from shared folder and I wont to save documet notepad++ freeze and crash. When I diesable this plugin problem does not exist.
I put my photos in their new
http://img689.imageshack.us/img689/2391/savedm.jpg
http://img341.imageshack.us/img341/6985/notsaved.jpg
Photos show that the option "saved" and "not saved" is not working properly.
I do not speak English, it explains to me what I am writing to Google. That is why I put photographs.