[Marble-devel] Getting trouble with regionSelected signal

[Anton Chernov]

Hello Torsten.

I made some investigations in regionSelecting function. I think bug
was in MarbleWidgetDefaultInputHandler::eventFilter function. We don't
need to make Rubber coordinates conversion from global.
The patch is applied. I tested it. Everything work correct now.

Another small change which presented in the patch is in
GeoDataParser.h, because current git version have compiling error in
MSVC2008.

Best regards,
Anton

2011/9/22 Torsten Rahn <tackat at t-online.de>:
> Hi,
>
> On Thursday, 22. September 2011 15:13:19 Anton Chernov wrote:
>> I'm developing simple application for bathymerty data management and
>> use Marble library as UI for selecting data.
>> I connect to signal MarbleWidget::regionSelected(QList<double>) and
>> process selection information in slot.
>
> Unfortunately the implementation of this particular method has been buggy
> right from the start. It has been introduced (and since used) by the Digikam
> application. :-/
>
> Best Regards,
> Torsten
>
>
>
>> But I found that very strange values are returned in QList<double>. It
>> have to be coordiantes of selected region but it is not so. Some times
>> values are "similar" to true but usually not. I have already tried to
>> change projection to Mercator the same problem - coordinates are
>> incorrect.
>>
>> I'm a newbie in Marble development and can't find a way myself. Please help
>> me.
>>
>> Best whishes,
>> Anton
>> _______________________________________________
>> Marble-devel mailing list
>> Marble-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/marble-devel
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: regionSelected.patch
Type: application/octet-stream
Size: 1352 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/marble-devel/attachments/20110923/e5e15ad9/attachment-0001.obj>