Opened 16 years ago

Closed 15 years ago

Last modified 15 years ago

#1306 closed patch (fixed)

Attribute table display problem when features already selected

Reported by: cfarmer Owned by: nobody
Priority: major: does not work as expected Milestone:
Component: Vectors Version: Trunk
Keywords: select, attribute table Cc:
Must Fix for Release: Yes Platform: All
Platform Version: Awaiting user input: no

Description

If a vector layer has features selected before opening it's attribute table, only those features previously selected are visible when the attribute table is opened.

Attachments (1)

bugfix1306.diff (5.2 KB ) - added by jef 16 years ago.

Download all attachments as: .zip

Change History (16)

comment:1 by cfarmer, 16 years ago

Must Fix for Release: NoYes

comment:2 by jef, 16 years ago

Resolution: invalid
Status: newclosed

That's intentional.

in reply to:  2 comment:3 by msieczka, 16 years ago

Resolution: invalid
Status: closedreopened

Replying to jef:

That's intentional.

I also noticed the issue cfarmer reported and thought it was an error. Now that I learned it's intentional I find it at least counter intuitive.

Why not, instead, only navigate to the selected row, still leaving the rest of the table visible? As it is now, users will ask where has their data gone.

comment:5 by msieczka, 16 years ago

Platform: LinuxAll

Confusing the user is not the way to solve performance issues with big tables IMO.

by jef, 16 years ago

Attachment: bugfix1306.diff added

in reply to:  5 ; comment:6 by jef, 16 years ago

Type: bugpatch

Now the behaviour is configurable. The attribute table either shows all featues (default), all selected features or all features in the current canvas.

comment:7 by jef, 15 years ago

newly selected features that are not present in the attribute table are now added.

comment:8 by jef, 15 years ago

in r9598 that is.

comment:9 by pcav, 15 years ago

I still have problems with this: once the table with selected elements is shown, how can a user select all the rows? Apparently pressing the first button has no effect

in reply to:  6 comment:10 by jef, 15 years ago

Replying to jef:

Now the behaviour is configurable. The attribute table either shows all featues (default), all selected features or all features in the current canvas.

Replying to pcav:

I still have problems with this: once the table with selected elements is shown, how can a user select all the rows? Apparently pressing the first button has no effect

The patch is still pending due to feature freeze. Once it's applied your your problem would be solved, wouldn't it?

comment:11 by wonder, 15 years ago

I think that the current behaviour is not acceptable for most users. Showing only selected rows is quite misleading (without telling user what's going on). It introduces new problems and it doesn't solve the real problem.

I vote for applying the patch before 1.0.

comment:12 by mhugent, 15 years ago

Well, the solution for the real problem would be 'better table' I guess. Looking closer at the patch, it seems quite unproblematic bug wise. Still we need to have the ok from the documentation team since it involves GUI changes. And translations are also not aware of the additional string.

comment:13 by mhugent, 15 years ago

I checked with Otto and it seems to be ok for the documentation team. Jürgen, could you please apply the patch? It seems that it needs some small changes to apply it to current svn trunk.

Thanks, Marco

comment:14 by jef, 15 years ago

Resolution: fixed
Status: reopenedclosed

applied in r9689

comment:15 by (none), 15 years ago

Milestone: Version 1.0.0

Milestone Version 1.0.0 deleted

Note: See TracTickets for help on using tickets.