Using the page test feature, the detection settings are set to the
default, based on the function defaultpage in
functions/functions.import.php. defaultpage relies on the config
When you import a new form, it will use these default settings. Then
the system will ask you to use the "page setup" feature. This allows
you to override the settings by moving the corner edge boxes which
will be stored in the database for that particular form.
Please check the 'pages' table in the database to see the settings for
that particular page in the form. You could modify the variables in
that table to match the default settings if they are different. Pay
particular attention to the VERT_WIDTH and HORI_WIDTH entries if you
are having corner edge detection issues.
Let me know how you go.
On 14 October 2012 12:35, David Burke <david@...> wrote:
> Ha actually what I said is inaccurate, I have a script to import new forms
> and it was pointing towards a old version of quexf causing me much
> Regardless I'm still seeing inconsistency between test compatibility and
> real scans. When I look in test compatibility with a scanned sheet it picks
> up the guide lines. When I process the same PDF, I can get inaccurate data.
> The is presumably because the scan line is not picked up correctly. But I
> can't debug it other than lots of trial and error. I can't get a visual of
> what's going on. Any ideas?
> On Sat, Oct 13, 2012 at 7:33 PM, David Burke <david@...>
>> Hello Adam,
>> I was playing around with the new "test form compatibility with queXF". I
>> see there are some config settings such as PAGE_GUIDE_X_PORTION that will
>> change the boxes where it looks for guide lines. This can sometimes be
>> required to change for a form to be compatible. I think one can safely
>> assume if the original pdf form requires this, all scanned forms would use
>> the same settings.
>> Currently in page setup the guide line box defaults to where it goes
>> without consideration to PAGE_GUIDE_X_PORTION. I think page setup should
>> consider these values. In many cases this would make page setup unnecessary
>> (which means less work for administrators). Thoughts?
>> I was debugging the code a little. I believe in
>> functions/functions.import.php defaultpage the x_portion is taken into
>> consideration. However in page setup it just get's whatever value happens to
>> be in the database. This value however is never explicitly set. It comes
>> from a default sql value as seen in database/quexf.sql
>> I suppose a fix would have to calculate the default values in new.php and
>> explicitly set them in the database.
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> Quexf-discuss mailing list
Research and Development Officer
Australian Consortium for Social and Political Research Inc.
+61 3 9013 9653