configuration of the esearch widget

[roialgavish]

Hello,
I have a number of questions about the configuration of the esearch widget, I am using the esearch 3.6.1 compiled version:

1-The main layer who I work with is a point layer. I am trying to set the zoom scale of my point layer, I tried a number of options and I didn???t succeed to set to zoom scale to my needs. It is important to note that I don???t want  that every time which I will press on one of the selections, the zoom will be larger. I just want to set the scale of the zoom, for the first click.

2-I am trying to understand how to enable export, the attribute table only shows data within the map extend and not the data from the esearch widget result. How can I define that the attribute table will take the data from the results window?

3-I am wondering if there is way to highlight the result of the search?

4-I am wondering if there is way to set the width of the text box?

I am asking these questions after I had already read the PDF help file, I hope that it will be possible to receive help.

Thank you all,
Roi Algavish.

[RobertScheitlin__GISP]

Roi,

1.    I am not 100% sure what your issue is with the zoom. If you set:



<zoomscale usegeometry="false">2400</zoomscale>

then it will zoom to that exact scale.

2. The eSearch widget does not have anything to do with the AttributeTableWidget. The eSearch widget uses it's own datagrid for displaying results. Consult the Enhanced Search Widget Fixed Datagrid Setup.pdf.


3. The results of the search can be highlighted with the subselection color when clicking on a record in the datagrid, once you fix your issue in question 2. Beyond that the answer would be No.


4. No, the width of the textbox is defined by the size of the widget

[roialgavish]

Hello Robert,

First I wanted to say thanks allot, the widget and your support is more than very helpful. I have done what you said and it worked perfectly. I have another issue who I can use some help.

When I am exporting my data, the file that is created is written in a format that is causing me some problems. When I open the csv file in the notepad it has quotations around a numeric field, and it has all the fields and the values without an end line, it just continues as one paragraph.  If I open the csv file in excel and save it, and open it again in notepad, it will open with each field in its own line, and the quotations don�??t appear.

What I am asking is: is there a way to export the numeric field without the quotations around it? So the computer will recognize it as a numeric field?

Again thank you very much.

[RobertScheitlin__GISP]

Roi,

   The export to csv was designed around the user using the csv file in Excel not notepad. Notepad is a fairly unintelligent program and does not understand the unix line endings of \n that are used in the export. This is something I can look at addressing in the next release.

   As far as the numeric data having text qualifiers around them. That is just the way it is. All data is treated as strings in the export. For the datagrid to know the columns datatype would involve a lot more code and user configuration than is currently present.

[roialgavish]

Robert,

The notepad was only a way to explain the difference in the format of the data, the export file is going to a CRM program which need the numeric value. I understand this is not possible, and I will try to find a different solution.

Thank you for your answers,
And for the widget.

[RobertScheitlin__GISP]

Roi,

   So I have thought about this more and when I add the field to the datagird I do know if they have been formated as numeric or currency so I could export those fields without the text qualifier.

[roialgavish]

Robert,

When I tried to specify the field as "numberformat" as instructed by the PDF file, It worked as far as the separators.
But it steel export it with the quotations around the value.

I didn�??t understood whether this is what you meant in your last answer or maybe to do something else?

Thank you.

[RobertScheitlin__GISP]

Roi,

   That is what I meant but I have not adding the code in the export routine to take into account that it is a number and that it could/should be handled differently. This is something that I am looking at for the next version.

[roialgavish]

Robert,

Again thank you very much.

Roi Algavish.