Bug 341750

Summary: Selected line doesn't stay in query data view
Product: [Applications] KEXI Reporter: robert leleu <robert.jean.leleu>
Component: QueriesAssignee: Kexi Bugs <kexi-bugs>
Status: CLOSED DUPLICATE    
Severity: wishlist CC: adam, inksi, staniek
Priority: NOR    
Version: 2.8.5   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description robert leleu 2014-12-10 16:46:35 UTC
Once a line has been selected. and is visible, if you exit the mouse from the query display windows, the list rolls back to the first row.
I would rather to have some possibility to let the list in position.

Reproducible: Always
Comment 1 Jarosław Staniek 2014-12-10 20:24:56 UTC
Thanks. Which view is that? data, visual or SQL?
Comment 2 robert leleu 2014-12-10 21:13:55 UTC
I beg you pardon...... data

la 10/12/2014 21:24, Jarosław Staniek skribis (esperanto estas la unua 
internacia lingvo)
> https://bugs.kde.org/show_bug.cgi?id=341750
>
> Jarosław Staniek <staniek@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |staniek@kde.org
>
> --- Comment #1 from Jarosław Staniek <staniek@kde.org> ---
> Thanks. Which view is that? data, visual or SQL?
>
Comment 3 Jarosław Staniek 2014-12-10 21:28:06 UTC
Does the same happen in table data view?

And rows take more than one screen vertically?

Please look at this bug fixed in 2.8.6: https://bugs.kde.org/show_bug.cgi?id=337914
Comment 4 robert leleu 2014-12-11 10:10:37 UTC
Not the same as https://bugs.kde.org/show_bug.cgi?id=337914
Once a row has been selected, if you draw the mouse out of the query window, the list rolls up to the first line, but the selected row is unchanged (although not visible). Then clicking any header rolls down the list so that the selected row is again visible.
Comment 5 Jarosław Staniek 2014-12-11 10:38:39 UTC
We'll know if we compare the versions... I still believe it's related and the fix addresses many related misbehavior. At least I am unable to reproduce with 2.8.7.

Any chance that you update to 2.8.7?
Comment 6 robert leleu 2014-12-11 13:22:09 UTC
Since Mint17 I've been unable to instull project neon, and, on another 
hand, I never succeeded to compile calligra. So I'm bound to 2.8.6. Now 
are holidays. I try next year.

Bonan novan jaron !


la 11/12/2014 11:38, Jarosław Staniek skribis (esperanto estas la unua 
internacia lingvo)
> https://bugs.kde.org/show_bug.cgi?id=341750
>
> Jarosław Staniek <staniek@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|UNCONFIRMED                 |NEEDSINFO
>           Resolution|---                         |WAITINGFORINFO
>
> --- Comment #5 from Jarosław Staniek <staniek@kde.org> ---
> We'll know if we compare the versions... I still believe it's related and the
> fix addresses many related misbehavior. At least I am unable to reproduce with
> 2.8.7.
>
> Any chance that you update to 2.8.7?
>
Comment 7 Jarosław Staniek 2014-12-11 14:37:21 UTC
Bonan novan jaron Robert!

Linux Mint 17 looks like a long term support release. I am wondering if it could be reasonable supported. A fix comes in July, we're in December and it's not available. This is frustrating and needs to be addressed.

Even 17.1 does not support their users very well.
http://packages.linuxmint.com/search.php?keyword=calligra&release=any&section=any
How is this long term support if software updates are not supported :)

Maybe heavy users like you can consider compiling or picking rolling-release-based distros.
Comment 8 robert leleu 2014-12-11 15:18:28 UTC
la 11/12/2014 15:37, Jarosław Staniek skribis (esperanto estas la unua 
internacia lingvo)
> https://bugs.kde.org/show_bug.cgi?id=341750
>
> --- Comment #7 from Jarosław Staniek <staniek@kde.org> ---
> Bonan novan jaron Robert!
>
> Linux Mint 17 looks like a long term support release. I am wondering if it
> could be reasonable supported. A fix comes in July, we're in December and it's
> not available. This is frustrating and needs to be addressed.
>
> Even 17.1 does not support their users very well.
> http://packages.linuxmint.com/search.php?keyword=calligra&release=any&section=any
> How is this long term support if software updates are not supported :)
>
> Maybe heavy users like you can consider compiling or picking
> rolling-release-based distros.
>

indeed. I checked this page this morning....

Which rolling release wold you recommond ? Mint debian ?
Comment 9 Jarosław Staniek 2014-12-12 15:18:26 UTC
> Which rolling release wold you recommond ? Mint debian ?
No opinion here, you'd need to look how recent Calligra these distros offer in 2014.

Traditional Kubuntu offers 2.8.7 today: http://www.kubuntu.org/news/calligra-287-out
Comment 10 Jarosław Staniek 2015-10-31 21:04:10 UTC
Assuming this is a duplicate. If 2.9.x shows the bug again we can easily reopen this bug. 
Thanks a lot.

*** This bug has been marked as a duplicate of bug 337914 ***