CudaText 1.101.5 beta

[Alexey-T]

win64
https://yadi.sk/d/6IYcAmNmKUG7Vw
win32
https://yadi.sk/d/iPq_Cy0ZT9r4Rg

@dinkumoil @kvichans @jairo-martinez

https://github.com/Alexey-T/CudaText/blob/master/app/readme/history.txt

[JairoMartinezA]

Hi @Alexey-T

About this option:

• add: option "ui_notif_confirm" to enable confirmation on file auto-reloading

Is this option for avoid the confirmation dialog to do the reload in silent way?

I see this value set by default to False but I have one scenario where I still see the confirmation dialog:

1. Open file with application A.
2. Open same file with Cud.
3. Make changes in file with application A and save the changes.
4. The changes are reloaded automatically in Cud.
5. Make one change with Cud and save.
6. Reload file in Application A to see the change.
7. Do another change in Application A and save.
8. Cud show again the confirmation dialog.

[Alexey-T]

even w/o option set, Cud must show confirm, when it has file modified (your steps don’t show that Cud copy is modified?? Strange)

[dinkumoil]

I can confirm the issue of @Jairo-Martinez.

It seems that Cud internally uses a flag to decide whether to show the confirmation dialog or not. I guess this flag is set when a user changes a document in Cud (in order to show the confirmation dialog when an external application changes the document too) but it is not reset after saving the changes in Cud.

[Aram-ops]

Добрый день , Алексей. Спасибо , что создали такой редактор. У меня вопрос к вам, как
настроить редактор , чтобы работало автозаполнение кавычек ? Скобки естественно в порядке.
Спасибо ,Вам,

[Alexey-T]

вот опять, пИшите не как надо. тут не обсуждение. тут анонс версии. вопросы надо на форум.
:(

[Alexey-T]

@dinkumoil @Jairo-Martinez @kvichans
reproduced that issue.
it occurs IF UndoCount of editor is >1, and UndoCount is >1 when you edit file and saved it (undo counter don't reset on save!!)
so - not a bug
confirmation is OK if UndoCount>1 to NOT LOOSE undo

[dinkumoil]

So, I would say the decision to show the confirmation dialog uses the wrong flag. It should not use _UndoCount_ but the _Dirty_ or _Changed_ flag of the document instead (don't know how you call it).

Just saw your edit:

to NOT LOOSE undo

Yes, that's worth to think about...

[Alexey-T]

@kvichans Seems your comment at forum- is reason why i added checking of UndoCount (Dirty-flag was chcked before)

[dinkumoil]

Thinking finished ;). I would say the current behaviour is OK. If a user edited a document he should be asked to reload it even if he already saved his changes.

[JairoMartinezA]

Thinking finished ;). I would say the current behavior is OK. If a user edited a document he should be asked to reload it even if he already saved his changes.

I not agree, I prefer like Notepad++ if I select Update silently no message is showed even if the change happens in Cud first, Intellij Idea by example do the same reloading modified files w/o confirmation dialog.

[Alexey-T]

Will change new opt to be integer, not Boolean

0 - always show confirm
1 - show confirm if file modified or undo count>1
2 - show confirm if file modified, like NP++

Ok?

[dinkumoil]

Having a choice is always the best.

[Alexey-T]

Ok, will be in next update

[Aram-ops]

Спасибо огромное!!!

[Alexey-T]

Release 1.101.5.