> > I meant after the drop. The first time I dropped I thought that > nothing had happened, because when I dropped it the action went back > to where it started, and then nothing else happened for some time, > probably less than a second but long enough to make me think the drag > had failed.
I understand what you mean now. I'll put it on the todo-list. I really don't know what is possible to do immediately (which is when > it needs to happen) so I'm afraid I don't have any decent suggestions- > maybe just ensure that the action doesn't return to the original > location, but immediately vanishes? maybe the 'thinking' spinning icon > should come up? > > >> * that said, I haven't used drag/drop since I did my initial cleanup > >> of tasks, so I wouldn't focus your time/energy too much on drag/drop. > >> :) > > > > Actually DnD is my favorite way to add dependencies, so I am interested > to > > hear any improvement suggestions. > > Hrm, interesting. I wonder why the difference. Do you find the > autocomplete awkward/too slow/too hard to remember the titles of the > other actions? I usually add a couple of actions as they pop into my head, and when I see them in front of me I might see that they are dependent on each other. Sometimes they might not be strictly dependent, but it gives me a way of presenting sequential actions. > >> * deleting dependencies (using the 'X' marked 'Remove the successor') > >> doesn't seem to work here (ffox 3.5, windows XP) > > > > This makes me wonder if you use the latest version. I applied Reinier's > > patch that should enable this function. I have experienced some problems > > with the javascript updates, so it might need a manual refresh in some > > cases. > > Ah, this is the patches from yesterday? I have not upgraded, am using > code from 48-72 hours ago. Apologies. I don't want to spam this list with commit info unless it is a release of some sort. I could of course email interested persons when I have committed something possibly interesting. > [upgraded now] > > So, I guess I assumed that the X deleted the dependency, rather than > making it return; now that I understand the behavior it makes more > sense. Maybe using language other than 'remove'? (But admittedly I > don't have a good suggestion on that right now.) A couple notes on it: > > * before the patch, there was some explanatory text when you hovered > over the X. This seems to be broken now? Will look into it. > > * when I hit the X on the main page, the successor action is removed > from the preceding action but doesn't show up again until a refresh, > so it looks like it was deleted. This works as expected in the project > view- weird. Probably "just a bug". Will look into it. /Henrik
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
