FW: [Qgis-developer] RE : Debugging QGIS Bugs

[Nathan Woodrow]

I agree with Andreas.  Popups are not good for this use case.    I just
think using: column IS NULL is correct for both cases and I think it would
confuse people to make them pick.

On Tue, Jan 18, 2011 at 11:33 PM, Andreas Neumann <a.neumann at carto.net>wrote:

>
> Hi,
>
> I'd rather prefer to have this as a setting somewhere instead of being
> interrupted in the search by a popup. Just as in web applications, in
> regular applications popup windows should be avoided, if possible.
>
> I think this could be a setting/option that should be saved in the project
> file, either
>
> * per dataset
> * per column
> * project setting
> * global setting (already possible now)
>
> In one of the recent check-ins from yesterday or today, Jürgen Fischer
> added a setting in "Options" --> "General" --> "Representation of NULL
> values" which allows for arbitrary strings to mean "NULL". One can use NULL
> in his own language, or as a number -9999, or whatever one likes.
>
> I think you should use this setting for the NULL searches and don't ask the
> user each and every time he is searching for NULL. This setting doesn't
> change frequently, so I think it is ok as a global setting, or maybe also a
> per project or dataset/column setting which can overwrite the global
> setting.
>
> Just my two cents,
>
> Thanks for working on it!
>
> Andreas
>
>
> On Tue, 18 Jan 2011 14:18:40 +0200, Tim Sutton wrote:
>
>> Hi
>>
>> Radio button one is probably more appropriate in this case.
>>
>> Regards
>>
>> Tim
>>
>> On Tue, Jan 18, 2011 at 1:17 PM, sunilraj.kiran
>> <sunilraj.kiran at kcubeconsulting.com> wrote:
>>
>>> Hello Tim,
>>>
>>>      I am working on the ticket https://trac.osgeo.org/qgis/ticket/2974.
>>> The ticket deals with Attribute search, as  there can be three ways of
>>> NULL
>>> searches were possible.
>>>
>>> i.e   1) searching records with NULL values.
>>>
>>>        2) searching records containing NULL as text string.
>>>
>>>        3) Both
>>>
>>>          The above ticket can be fixed by designing a New Widget
>>> displaying
>>> the above options. If the user has entered NULL in the Search string Edit
>>> box in the attribute table dialog the particular Widget could Pop up to
>>> ask
>>> user’s choice and the result will display the selected records.
>>>
>>> I have attached two screenshots containing two designs for the particular
>>> Pop up Widget. Can you please have a look at it and let me know whether
>>> this
>>> suggestion is fine or not?
>>>
>>> Regards,
>>>
>>> Sunil
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> From: Nathan Woodrow [mailto:madmanwoo at gmail.com]
>>> Sent: Thursday, January 13, 2011 5:21 PM
>>> To: sunilraj.kiran
>>> Cc: Jürgen E. Fischer; qgis-developer at lists.osgeo.org
>>> Subject: Re: [Qgis-developer] RE : Debugging QGIS Bugs
>>>
>>>
>>>
>>> I believe he is talking about null as in no value. This is the kind
>>> of behavior that I would use.
>>>
>>> 2011/1/13 sunilraj.kiran <sunilraj.kiran at kcubeconsulting.com>
>>>
>>> Hello Everyone,
>>>
>>>      I am working on the below ticket. While proceeding I came through
>>> with
>>> a question, whether we should deal the particular bug either with "null"
>>> which means no value or with "null" which is a text null ?
>>>
>>> https://trac.osgeo.org/qgis/ticket/2974
>>>
>>> Regards,
>>> Sunil
>>>
>>> _______________________________________________
>>> Qgis-developer mailing list
>>> Qgis-developer at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>
>>>
>>>
> --
> --
> Andreas Neumann
> Böschacherstrasse 10A
> 8624 Grüt (Gossau ZH)
> Switzerland
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/qgis-developer/attachments/20110118/4d04eff0/attachment-0001.html