BUG: Slow keyboard input in Comments when 'Window fading' is enabled in preferences

[.dan.g.]

Originally from GitHub by mosca

If I have EnableLightboxMgr=1 in the Preferences section of my ToDoList.ini, then the Comments editor (both Rich and Simple text) becomes sluggish (I can type faster than it can update).
If EnableLightboxMgr=0, the Comments editor becomes very fast, it updates instantly.

...

To double-check my statement about the EnableLightboxMgr setting, I repeated the test a few minutes ago. I switched it to 1 in the INI file (after closing Todolist). Then I started Todolist and the Comments editor became slow. Switching it to 0 removed the problem. When the setting is 1, the editor prints the typed characters about 2-3 times slower than when the setting is 0.
By the way, what does this setting influence? Can I also change it from the Preferences menu? So far I always changed it in the INI file with a text editor.

...

I tested the problem by switching the 'Enable window fading' option on and off in the Preferences window, and it slows down or speeds up the Comments window the same way when I changed this setting in the INI file.

The speed difference is very noticeable even when I hold down one key only.

[sinjin tang]

I am running Todolist in Virtualbox (win xp) on a Linux machine. I too was experiencing serious keyboard lag issues. This post helped. Turning off "Enable window fading" fixed the problem. Thanks

[.dan.g.]

I will disable that feature by default in the next update, with a view to removing it altogether in a future release.

[Polisson]

In my case, the problem still exists and changing any of those two options doesn't work - Comment field is very slow responding.

[.dan.g.]

Hi Polisson

Can you post a screenshot of the whole app pls?

[Polisson]

Yes, of course. In attachment. 

[.dan.g.]

Thx Polisson.

I notice that you are on version 7.0.1. Can you update to 7.0.7 and confirm that the problem still exists pls?

Dan

[Polisson]

Hmmm.... before I posted first time, I've updated my app to newest ver. So how do you suppose that I use old ver? 

That's true that my task list file was used with few old versions of ToDoList and I can't build it from scratch

[.dan.g.]

>> So how do you suppose that I use old ver?

My mistake, I was looking at the old version category at the top of the post which hadn't been updated.

Some more questions:

1. If you hold down a character key in the comments, do you notice any flickering of the tasklist?

2. If you switch to 'Sort > Unsorted' does this make any difference?

3. Is there any difference between simple and rich text comments?

Dan

[Polisson]

Unfortunately none of those 3 aspects does affect this issue. So 3xNO ;/ but there is one more thing that I've noticed since trying to fix that bug: sluggish typing is sometimes present in 'Title' field of task. I don't know how to trigger it, so it's spontaneous for me.

One question: has the app any type of debug mode? or can I find any log to post it here for more efficient help or improve app? because I like it so much :)

[Polisson]

I've noticed one more thing: problem persists only in my old .tdl file which I use circa about 1 year. I've checked that issue appeared in ver. 7 (old backup of app works well with old backup of tdl file). New files crated with current version hasn't this problem, but my old file is very important so I can't to obsolete it. Also, I can't downgrade app, cause my file was updated by new-ver, so tdl is non-editable by old-ver one.

[.dan.g.]

Thx Polisson.

If I were to guess, I would say that it was the combination of the tasklist and your preferences.

As such, we've reached the stage where I'll need you to send me a copy of the tasklist and the preferences file if I'm to look into this more.

I'll understand if you are reluctant to do this but over the years I've not found any alternative to working with the problem data itself...

abstractspoon2(at)optusnet(dot)com(dot)au.

Rgds

Dan

[.dan.g.]

Should be fixed in 7.0.9. Can you confirm pls?

On Tuesday, 17 November 2015 00:11:48 UTC+11, Polisson wrote:

[Mateusz Polak]

Yes! Works great now! Thanks a lot! :)

Just after updating I've noticed that, sluggish response of comment window was gone, but at the same time one more problem appeared. I thought it is common to this last one which You've fixed but not and something else causes it. Unfortunately I can't reproduce it.

This problem is editing "Time Spent" field after a time tracking was stopped. During time tracking, editing this field is locked (it is disabled and greyed), but in some cases when I stop time tracking, the field becomes white (like enabled) but I can't edit its value. In my case it happens quite  often because when something disturbs my work, I forget to stop tracking and when I back to the business after few hours, I need to edit this value. So then I stop the tracking and try to edit only restarting of app allows to do it.

As I said, I can't trigger it, so seems to be spontaneous for me now ;)

I will try to observe what I do to find the cause.

--
Download Latest Version: http://abstractspoon.pbworks.com/f/todolist_exe.zip
Wiki and other resources: https://github.com/abstractspoon/ToDoList_Wiki/wiki
---
You received this message because you are subscribed to a topic in the Google Groups "ToDoList (AbstractSpoon) Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/abstractspoon-todolist-support/I8FeQ0LGaUQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to abstractspoon-todolis...@googlegroups.com.
To post to this group, send email to abstractspoon-t...@googlegroups.com.
Visit this group at http://groups.google.com/group/abstractspoon-todolist-support.

To view this discussion on the web, visit https://groups.google.com/d/msgid/abstractspoon-todolist-support/24e6269c-6b46-4a94-b8c5-0b9e464983fd%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Hotmail]

Please set this topic to „fixed /solved / erledigt“

[.dan.g.]

>> sluggish response of comment window was gone

I'm glad and thx for your help in fixing it.

>> I will try to observe what I do to find the cause.

Many thx Mateusz.

ps. If/when you do find the sequence that produces it can you post that as a new bug pls?