BUG: collision between values in "allocated by" & "allocated to" fields

18 views
Skip to first unread message

Lior Sheinmel

unread,
Sep 16, 2015, 1:25:27 PM9/16/15
to abstractspoon-t...@googlegroups.com

ver 7.02 with ini file (not registry)

reproducing the bug


1. create  same 10 different values in "alloc by" & "alloc to", meaning for example
10 different persons which their names are used both in the "alloc by" & "alloc to" fields 

2, use all of the 10 values in the "alloc by" & "alloc to"

3, change the entries in "alloc by" to use just 7 out of 10 possible values (but in the allocated to keep all the 10 values)

4. delete the 3 unwanted valued in "alloc by" combobox (now there should be just 7 values)

5, save the tdl file, close it and open it again

6. are all the 10 values appear in the "alloc by" field (include the 3 values which are not used any more in the "alloc by" field, but still being used in the "allocated to" field)?

tnx 

Lior

Tony G

unread,
Sep 16, 2015, 1:54:21 PM9/16/15
to abstractspoon-t...@googlegroups.com
I think I see the confusion.
The Alloc By field is stored in the XML with a node ALLOCATEDBY. The Alloc To field is stored in the XML with a node PERSON. It's pure coincidence that you have a PERSON and an ALLOCATEDBY with the same name.

While on one hand it's good that those are separate lists, in hindsight one could suggest that Dan could have named those differently, or perhaps PERSON could have optionally been used for both lists. But I doubt this will ever get changed simply because 'stuff" like stylesheets and programs have been built around the current structure.

If you have set any names in Preferences for the dynamic dropdowns, Those names are saved in the INI, at a global level rather than at the tasklist level.

So the bottom line here is that if you really need to remove someone, you need to delete them from both the By and To lists.


[EDIT] Having said that, if you say you've deleted the people from one list or the other, and they are not used in any other tasks (use the filter to check), and refreshed the .tdl, and those people are still in the list, then yes, that sounds like an issue.


HTH
T

.dan.g.

unread,
Sep 16, 2015, 8:13:28 PM9/16/15
to ToDoList (AbstractSpoon) Support
In fact, the problem was simply a typo in the code that loaded the 'Alloc To' values into the 'Alloc By' list by mistake.

I'll get this fixed for 7.0.3.

ps. I agree that this will always be confusing for stylesheet writers.

Lior Sheinmel

unread,
Sep 17, 2015, 2:45:56 AM9/17/15
to ToDoList (AbstractSpoon) Support
does this bug efect more fields ?

Daniel Godson

unread,
Sep 17, 2015, 2:55:03 AM9/17/15
to ToDoList (AbstractSpoon) Support
No, it was a one line error caused by copying the 'AllocTo' code and failing to change it to 'AllocBy'.


--
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 the Google Groups "ToDoList (AbstractSpoon) Support" group.
To unsubscribe from this group and stop receiving emails from it, 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/20f194f4-73aa-4ab5-ba49-776c5c5011d3%40googlegroups.com.

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

Reply all
Reply to author
Forward
0 new messages