Custom project area does not move - some tasks are hided under databanks

Voted for this task.

Voted for this task.

To see all the tasks you can resize the databank or the tasks panel itself.

We changed the way how the tasks are displayed in build 135 to multi column layout - see the printscreen

but assume that we want to see tasks in one column, to use space efficiently.

all lower tasks are now below databanks, and everytime we need to see or change any task, we should minimize databanks, and then re-open it.

multi column layout is ok, but this is the problem.

Please recheck.

Voted for this task.

Huh?

It's just common sense, the main section operates properly (well, vertically anyways), we can make the databank big or small and we can always scroll the main window and see EVERYTHING why would you make the task list function differently? Nobody will enjoy having to move the databank out of the way just to see the bottom tasks! What an annoyance! Please do fix.

And sliding the task list to be wider is not a good solution because I don't WANT to give up valuable main tab real estate just because I have 20 tasks and now we can't see parts of the main section because the HORIZONTAL scrolling of the main section is also BROKEN IN A SIMILAR WAY, also, people with hundreds of tasks are still in a bind. Please do fix. 

The goal is we should be able to ALWAYS see ALL of the entire sections by SLIDING THE SLIDERS. That's the whole purpose of the slider system! We should never have to RESIZE something so we can VIEW SOMETHING ELSE.

Voted for this task.

Voted for this task.

To be clear there are 2 separate problems, 

1. if I widen the task list I can no longer find the START BUTTON, not even by scrolling.

2. if I have any databank showing then I can not see the bottom of the task list AREA (not even by scrolling) including when having 1,2 or 3 or more columns of tasks in cases where the list has too many tasks to show fully above the databank.

Greatly explained by bentra.

Thank you :-)

Voted for this task.

Voted for this task.

This is milestone 136 dev 5 and also marked fixed yet it is not fixed in 136 dev 6

Hi Bentra,

It will be fixed in the next dev. 
Yes. I missed out on some code when committing. Sorry, my bad.

Thank you.

Voted for this task.