next »

[Walton G.]

Hi, we often use the spellchecker for TEXTEDIT fields and this works fine.

However, as part of a project to have certain fields for case-insensitive searching (with code behind it), we are indicating these fields as BUTTONEDIT - so we can use the 'IMAGE' clause. See attached image. This helps users know which fields are case-insensitive.

By using BUTTONEDIT, the spellchecker no longer works and I do not see why it can't be.

Therefore, my suggestion is, can the spelling clause be added to BUTTONEDIT as well as TEXTEDIT?

Thanks


    BUTTONEDIT f6a = table.add_1,
    IMAGE = "textfontsizeup",
    STYLE="spellgb",                      <-- ** DOESN'T WORK **
    COMMENTS = "Address line 1";

[Reuben B.]

I won't answer the question directly, I'll leave that for the developers to comment.

However rather than misusing a buttonedit to add an image and identify special fields, did you consider using Presentation Styles either backgroundColor or backgroundImage?

Secondly your screenshot indicates you have address fields and you are presumably looking to make sure the address is entered correctly.  You could still use a TextEdit and add some logic to concatenate your 4 address fields into 1 string for the textedit, and split the resulting string back into your 4 address fields on the way out.  The question can also be asked, do you still need 4 address fields, they tend to be a hangover from character screens.

Finally if you are checking addresses, there are web services around that do address validation.  Even the Google Geocoding API can be used.  You had an Irish address so I'll illustrate with our Irish address, if I spell address correctly, the geocode API returns a result https://maps.googleapis.com/maps/api/geocode/json?address=Smithstown+Industrial+Estate,Shannon,Ireland

if I do a misspelling e.g. Smithtown instead of Smithstown, https://maps.googleapis.com/maps/api/geocode/json?address=Smithtown+Industrial+Estate,Shannon,Ireland Google is clever enough to make an intelligent guess and suggest the correct address, the formatted_address and partial_match fields can be used to identify if this has occurred.

Hope that helps

Reuben

[Walton G.]

Hi Reuben, many thanks for your reply. I think the point is, why put a restriction on buttonedit? I don't regard it as mis-using buttonedit. It actually works quite well apart from the spell bit. Actually, it is the comments field that is causing the issue as we don't spell check the address lines. I'm allowing case-insensitive searching on comments. The point of the image is merely to indicate to the user which fields (out of many!) are case-insensitive.

The problem with the address fields is long-standing and our users use it differently. Also, the DB is built around four address lines so we're pretty much stuck with it!

Thanks again, Reuben and I will check out the links.

All the best,

Gary

[.]

Hi Gary,

There was a GDC feature request registered to get a spell checker for form fields other than TextEdit: GDC-1321.
But it was been stated as "Won't fix" due to limitation in Qt.
So for now, it isn't planned to be implemented.

Best Regards,
Guney