----- Original Message ----- 
From: Steven E. Patamia, Ph.D.<mailto:[EMAIL PROTECTED]> 
To: Robert Kendall<mailto:[EMAIL PROTECTED]> 
Sent: Wednesday, April 09, 2008 2:52 PM
Subject: Re: DPMouse Field-Skipping under DP26x


You are welcome.  Sorry I could not do more.  I am relieved that you at least 
have a workaround.  You might try to contact the originators of version x and 
pass my comments to them.  Who knows .... maybe they will recognize something 
they can do about it.


2008/4/9 Robert Kendall <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>:

  For now I think I will switch back to DP26F. I can find a workaround to avoid 
using bolds in report variables and I definitely don't want to compromise the 
field-skipping function. Thanks so much for your attention.
    ----- Original Message ----- 
    From: Steven E. Patamia, Ph.D.<mailto:[EMAIL PROTECTED]> 
    To: Robert Kendall<mailto:[EMAIL PROTECTED]> 
    Sent: Wednesday, April 09, 2008 1:11 PM
    Subject: Re: DPMouse Field-Skipping under DP26x


    Hi Robert,

        From reading your explanation of the behaviour under DP26x my tentative 
conclusion is that the DPMouse code that determines whether to skip is being 
executed twice.  I do not know why, but it no doubt relates to something going 
on in DP26x as opposed to DP26f.  Probably it has to do with a delay in 
executing the Tab.  If that were to happen,  the DPMouse would submit the Tab, 
expect it to have been processed, and then when it was not processed, would 
look at the field again and decide to submit the Tab again.  At that point the 
first Tab would finally get processed and then he second one would folllow on.

       I, of course, have no control over what DP26x does, but I am not saying 
that just as a cop-out.  Really have no way to deal with it at all.  At this 
stage I also may not have a way to mitigate it either.  

       Remarkably, DPMouse survived Win98, Win2000, and WinXP.  I have even 
tested applications under Vista.  It survived a bunch of versions of DP itself. 
 Maybe we finally reached a version of DP that did something that DPMouse could 
not have anticipated.  Maybe its just an unintended consequence.  I just don't 
know.

         I am happy to continue to think about it and imagine a way of dealing 
with it, but I am not optimistic I can come up with anything.  Again, that's 
not a cop-out --- just honesty.

    On Wed, Apr 9, 2008 at 11:05 AM, Robert Kendall <[EMAIL 
PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:

      I am using Windows XP Pro. 

      I tried setting up a test panel with  5 fields. 1,2,4 and 5 are U10. 3 is 
U1::C for the field-skip dot. If field1 > "" then "∙" else "" endif. Under 
DP26f the tab works fine and if I enter something in field1 the cursor skips to 
field4 as desired. Under DP26x the tab work fine if field3 is "" but if field 1 
has data, the the dot shows in field3 and the cursor skips to field5 (not 
field4). I can shift-tab back to field4, but if I tab from field1 the cursor 
always skips twice to field5. I also tried removiing the field5. Under DP26X 
the tab works fine but once the field-skip is active the cursor won't leave 
field1 and I can't even tab to field2. 
        ----- Original Message ----- 
        From: Steven E. Patamia, Ph.D.<mailto:[EMAIL PROTECTED]> 
        To: Robert I Kendall<mailto:[EMAIL PROTECTED]> 
        Sent: Tuesday, April 08, 2008 4:46 PM
        Subject: Re: DPMouse Field-Skipping under DP26x


        hmmm...

            In your reply to this, please also indicate the Operating System 
environment (Win2000, XP etc).

            Well, what DPMouse does with respect to skip codes is internally 
generate a Tab to jump out of the field (as best as I can still recall -- its 
either a Tab or some similar simulated keypress that accomplishes  a jump to 
the next field).   To find the skip code, it simply reads the screen in the 
vicinity of the current field.  Logically, it cannot do more or less.  

            Having said that, try the following experiment:

            Temporartily remove the skip code next to a field.  When on that 
field, go ahead and manually press a Tab or whatever other key would take you 
to the next field (without a skip code of its own).  See what happens.  Is it 
different in DP26f versus DP26x?   Perahps in playing with this you will notice 
something.  Truly something has to be different.  See what you can notice and 
let me know.


         
        On Tue, Apr 8, 2008 at 2:17 PM, Robert I Kendall <[EMAIL 
PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:

          I am using DPSpool so I can put a letterhead image on my reports. In 
order to print bold text from within report variables, I need to use the ;;V 
field attribute available in DP26x. Otherwise the control characters do not get 
to DPSpool. At least that my understanding from Tim Rude.

          Sent from my iPhone


        -- 
        Steven E. Patamia, Ph.D., J.D.
        Personal Cell: (352) 219-6592 



    -- 
    Steven E. Patamia, Ph.D., J.D.
    Personal Cell: (352) 219-6592 



-- 
Steven E. Patamia, Ph.D., J.D.
Personal Cell: (352) 219-6592 
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf

Reply via email to