Hi, to Chris and company. I'm the doc who runs an electronic medical records
system on Motion tablets using remote desk top with the program running in a
thin client configuration. I last accessed the forum in September with hopes
that there would be a fix for the handwriting recognition problem over a
network in sp2.

-to recap, still using sp1 we can call up a floating tips panel and its
output will be recognized over the network, inputting into text fields
residing in server memory. This did not work in the beginning, but MS quickly
supplied a server OS patch which fixed the problem.

In sp2 the keyboard tips works, but 1. it takes up a lot of essential screen
real estate, & 2. it stretches across the whole screen (we have to run the
program in landscape) and, as we can't seem to reformat the tips keyboard
very well, the keys are so stretched out that it really slows down entry --
lot of side ways, back and forth tapping!

We would like to be able to use the the hand writing recognition engine in
sp 2 as its reputedly better.

Any inside word you knowledgeable folks have about a fix?
-- Jon

Nothing has changed in the behaviour of the in-place Input Panel that has
been officially posted. As for whether anything is planned, or what it might
be, we wouldn't be able to say, even if we _did_ know.

One thing I think you _should_ do is open a support case on it. Yes, it will
probably cost you, since the current behaviour is considered As Designed, not
a bug. But it will do two things -- remind them that they've created an
issue, and get you on the list if they actually prepare and issue a change.

I'm sorry, I wish I had a better answer. Especially since this change would
benefit me personally as well. Assuming it was a "tri-state" solution. I
wouldn't be willing to give up my floating, context sensitive, Input Panel
just to get the old SP1 behaviour.

--
Charlie.

doc jon wrote:
> Hi, to Chris and company. I'm the doc who runs an electronic medical
> records system on Motion tablets using remote desk top with the
> program running in a thin client configuration. I last accessed the
> forum in September with hopes that there would be a fix for the
> handwriting recognition problem over a network in sp2.
>
> -to recap, still using sp1 we can call up a floating tips panel and
> its output will be recognized over the network, inputting into text
> fields residing in server memory. This did not work in the beginning,
> but MS quickly supplied a server OS patch which fixed the problem.
>
> In sp2 the keyboard tips works, but 1. it takes up a lot of essential
> screen real estate, & 2. it stretches across the whole screen (we
> have to run the program in landscape) and, as we can't seem to
> reformat the tips keyboard very well, the keys are so stretched out
> that it really slows down entry -- lot of side ways, back and forth
> tapping!
>
> We would like to be able to use the the hand writing recognition
> engine in sp 2 as its reputedly better.
>
> Any inside word you knowledgeable folks have about a fix?
> -- Jon

As Charlie already posted, there's no solution (even a hint of one) at this
point. I would very strongly suggest filing a suggestion with Microsoft:
http://register.microsoft.com/mswish/suggestion.asp (Use "other" in the
Product: selection box) with the details. You might even cite Charlie's
Expert Zone article, Using Input Panel During a Remote Desktop Session
(http://www.microsoft.com/windowsxp/u...motedsktp.mspx)
as a "method," but unacceptable work-around in every-day use.
--
Chris H.
Microsoft Windows MVP/Tablet PC
Tablet Creations - http://nicecreations.us/
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone


"doc jon" <docjon@discussions.microsoft.com> wrote in message
news:05C116DB-D22B-4D42-B4BD-84AC7947650C@microsoft.com...
> Hi, to Chris and company. I'm the doc who runs an electronic medical
> records
> system on Motion tablets using remote desk top with the program running in
> a
> thin client configuration. I last accessed the forum in September with
> hopes
> that there would be a fix for the handwriting recognition problem over a
> network in sp2.
>
> -to recap, still using sp1 we can call up a floating tips panel and its
> output will be recognized over the network, inputting into text fields
> residing in server memory. This did not work in the beginning, but MS
> quickly
> supplied a server OS patch which fixed the problem.
>
> In sp2 the keyboard tips works, but 1. it takes up a lot of essential
> screen
> real estate, & 2. it stretches across the whole screen (we have to run the
> program in landscape) and, as we can't seem to reformat the tips keyboard
> very well, the keys are so stretched out that it really slows down
> entry --
> lot of side ways, back and forth tapping!
>
> We would like to be able to use the the hand writing recognition engine in
> sp 2 as its reputedly better.
>
> Any inside word you knowledgeable folks have about a fix?
> -- Jon

thanks, Charlie, I'll contact MS regarding a case.

"Charlie Russel - MVP" wrote:

> Nothing has changed in the behaviour of the in-place Input Panel that has
> been officially posted. As for whether anything is planned, or what it might
> be, we wouldn't be able to say, even if we _did_ know.
>
> One thing I think you _should_ do is open a support case on it. Yes, it will
> probably cost you, since the current behaviour is considered As Designed, not
> a bug. But it will do two things -- remind them that they've created an
> issue, and get you on the list if they actually prepare and issue a change.
>
> I'm sorry, I wish I had a better answer. Especially since this change would
> benefit me personally as well. Assuming it was a "tri-state" solution. I
> wouldn't be willing to give up my floating, context sensitive, Input Panel
> just to get the old SP1 behaviour.
>
> --
> Charlie.
>
> doc jon wrote:
> > Hi, to Chris and company. I'm the doc who runs an electronic medical
> > records system on Motion tablets using remote desk top with the
> > program running in a thin client configuration. I last accessed the
> > forum in September with hopes that there would be a fix for the
> > handwriting recognition problem over a network in sp2.
> >
> > -to recap, still using sp1 we can call up a floating tips panel and
> > its output will be recognized over the network, inputting into text
> > fields residing in server memory. This did not work in the beginning,
> > but MS quickly supplied a server OS patch which fixed the problem.
> >
> > In sp2 the keyboard tips works, but 1. it takes up a lot of essential
> > screen real estate, & 2. it stretches across the whole screen (we
> > have to run the program in landscape) and, as we can't seem to
> > reformat the tips keyboard very well, the keys are so stretched out
> > that it really slows down entry -- lot of side ways, back and forth
> > tapping!
> >
> > We would like to be able to use the the hand writing recognition
> > engine in sp 2 as its reputedly better.
> >
> > Any inside word you knowledgeable folks have about a fix?
> > -- Jon
>
>
>

Good point about the suggestion -- it's free, where the support case won't
be. (and I would certainly agree that my column workaround is woefully
inadequate at best.)

--
Charlie.

Chris H. wrote:
> As Charlie already posted, there's no solution (even a hint of one)
> at this point. I would very strongly suggest filing a suggestion
> with Microsoft: http://register.microsoft.com/mswish/suggestion.asp
> (Use "other" in the Product: selection box) with the details. You
> might even cite Charlie's Expert Zone article, Using Input Panel
> During a Remote Desktop Session
> (http://www.microsoft.com/windowsxp/u...motedsktp.mspx)
> as a "method," but unacceptable work-around in every-day use.
> "doc jon" <docjon@discussions.microsoft.com> wrote in message
> news:05C116DB-D22B-4D42-B4BD-84AC7947650C@microsoft.com...
>> Hi, to Chris and company. I'm the doc who runs an electronic medical
>> records
>> system on Motion tablets using remote desk top with the program
>> running in a
>> thin client configuration. I last accessed the forum in September
>> with hopes
>> that there would be a fix for the handwriting recognition problem
>> over a network in sp2.
>>
>> -to recap, still using sp1 we can call up a floating tips panel and
>> its output will be recognized over the network, inputting into text
>> fields residing in server memory. This did not work in the
>> beginning, but MS quickly
>> supplied a server OS patch which fixed the problem.
>>
>> In sp2 the keyboard tips works, but 1. it takes up a lot of essential
>> screen
>> real estate, & 2. it stretches across the whole screen (we have to
>> run the program in landscape) and, as we can't seem to reformat the
>> tips keyboard very well, the keys are so stretched out that it
>> really slows down entry --
>> lot of side ways, back and forth tapping!
>>
>> We would like to be able to use the the hand writing recognition
>> engine in sp 2 as its reputedly better.
>>
>> Any inside word you knowledgeable folks have about a fix?
>> -- Jon

Now I'm a bit unsure. It's been months since I had sp2 running on my motion
then uninstalled it because mentioned problems. I'm running RDS/WTS; I could
only use the onscreen keyboard, not the handwriting recognition TIPS, as its
ASCII output seemed not to be transmitted into the text fields in programs
running on the server. But you are indicating, Charlie, that handwriting
recognition does work over a network? Jon

"Charlie Russel - MVP" wrote:

> Good point about the suggestion -- it's free, where the support case won't
> be. (and I would certainly agree that my column workaround is woefully
> inadequate at best.)
>
> --
> Charlie.
>
> Chris H. wrote:
> > As Charlie already posted, there's no solution (even a hint of one)
> > at this point. I would very strongly suggest filing a suggestion
> > with Microsoft: http://register.microsoft.com/mswish/suggestion.asp
> > (Use "other" in the Product: selection box) with the details. You
> > might even cite Charlie's Expert Zone article, Using Input Panel
> > During a Remote Desktop Session
> > (http://www.microsoft.com/windowsxp/u...motedsktp.mspx)
> > as a "method," but unacceptable work-around in every-day use.
> > "doc jon" <docjon@discussions.microsoft.com> wrote in message
> > news:05C116DB-D22B-4D42-B4BD-84AC7947650C@microsoft.com...
> >> Hi, to Chris and company. I'm the doc who runs an electronic medical
> >> records
> >> system on Motion tablets using remote desk top with the program
> >> running in a
> >> thin client configuration. I last accessed the forum in September
> >> with hopes
> >> that there would be a fix for the handwriting recognition problem
> >> over a network in sp2.
> >>
> >> -to recap, still using sp1 we can call up a floating tips panel and
> >> its output will be recognized over the network, inputting into text
> >> fields residing in server memory. This did not work in the
> >> beginning, but MS quickly
> >> supplied a server OS patch which fixed the problem.
> >>
> >> In sp2 the keyboard tips works, but 1. it takes up a lot of essential
> >> screen
> >> real estate, & 2. it stretches across the whole screen (we have to
> >> run the program in landscape) and, as we can't seem to reformat the
> >> tips keyboard very well, the keys are so stretched out that it
> >> really slows down entry --
> >> lot of side ways, back and forth tapping!
> >>
> >> We would like to be able to use the the hand writing recognition
> >> engine in sp 2 as its reputedly better.
> >>
> >> Any inside word you knowledgeable folks have about a fix?
> >> -- Jon
>
>
>

Sort of. First, read the column that Chris referenced. Here's what works,
basically.

* Open the fixed TIP -- either at the bottom or the top of the screen, your
choice. Bottom it will always stay its current size. Top, it will
automatically grow and add additional lines.

* Now, make your remote connection. The TIP stays open, on top of the remote
window. I like to size the remote window to just above the TIP. And I set my
task bar on the Motion to autohide to maximize space.

* Now, work away in the remote window. If you need to enter text, write it
into the TIP at the bottom. Normal recognition will occur and when it says
what you want. insert it into the application.

It's kludgy, and real estate is an issue. But it does allow you to get some
work done.


--
Charlie.

doc jon wrote:
> Now I'm a bit unsure. It's been months since I had sp2 running on my
> motion then uninstalled it because mentioned problems. I'm running
> RDS/WTS; I could only use the onscreen keyboard, not the handwriting
> recognition TIPS, as its ASCII output seemed not to be transmitted
> into the text fields in programs running on the server. But you are
> indicating, Charlie, that handwriting recognition does work over a
> network? Jon
>
> "Charlie Russel - MVP" wrote:
>
>> Good point about the suggestion -- it's free, where the support case
>> won't be. (and I would certainly agree that my column workaround is
>> woefully inadequate at best.)
>>
>> --
>> Charlie.
>>
>> Chris H. wrote:
>>> As Charlie already posted, there's no solution (even a hint of one)
>>> at this point. I would very strongly suggest filing a suggestion
>>> with Microsoft: http://register.microsoft.com/mswish/suggestion.asp
>>> (Use "other" in the Product: selection box) with the details. You
>>> might even cite Charlie's Expert Zone article, Using Input Panel
>>> During a Remote Desktop Session
>>> (http://www.microsoft.com/windowsxp/u...motedsktp.mspx)
>>> as a "method," but unacceptable work-around in every-day use.
>>> "doc jon" <docjon@discussions.microsoft.com> wrote in message
>>> news:05C116DB-D22B-4D42-B4BD-84AC7947650C@microsoft.com...
>>>> Hi, to Chris and company. I'm the doc who runs an electronic
>>>> medical records
>>>> system on Motion tablets using remote desk top with the program
>>>> running in a
>>>> thin client configuration. I last accessed the forum in September
>>>> with hopes
>>>> that there would be a fix for the handwriting recognition problem
>>>> over a network in sp2.
>>>>
>>>> -to recap, still using sp1 we can call up a floating tips panel and
>>>> its output will be recognized over the network, inputting into text
>>>> fields residing in server memory. This did not work in the
>>>> beginning, but MS quickly
>>>> supplied a server OS patch which fixed the problem.
>>>>
>>>> In sp2 the keyboard tips works, but 1. it takes up a lot of
>>>> essential screen
>>>> real estate, & 2. it stretches across the whole screen (we have to
>>>> run the program in landscape) and, as we can't seem to reformat the
>>>> tips keyboard very well, the keys are so stretched out that it
>>>> really slows down entry --
>>>> lot of side ways, back and forth tapping!
>>>>
>>>> We would like to be able to use the the hand writing recognition
>>>> engine in sp 2 as its reputedly better.
>>>>
>>>> Any inside word you knowledgeable folks have about a fix?
>>>> -- Jon

One other point -- you need to make sure that the remote window is the
"active" window when you insert text from handwriting.

--
Charlie.

doc jon wrote:
> Now I'm a bit unsure. It's been months since I had sp2 running on my
> motion then uninstalled it because mentioned problems. I'm running
> RDS/WTS; I could only use the onscreen keyboard, not the handwriting
> recognition TIPS, as its ASCII output seemed not to be transmitted
> into the text fields in programs running on the server. But you are
> indicating, Charlie, that handwriting recognition does work over a
> network? Jon
>
> "Charlie Russel - MVP" wrote:
>
>> Good point about the suggestion -- it's free, where the support case
>> won't be. (and I would certainly agree that my column workaround is
>> woefully inadequate at best.)
>>
>> --
>> Charlie.
>>
>> Chris H. wrote:
>>> As Charlie already posted, there's no solution (even a hint of one)
>>> at this point. I would very strongly suggest filing a suggestion
>>> with Microsoft: http://register.microsoft.com/mswish/suggestion.asp
>>> (Use "other" in the Product: selection box) with the details. You
>>> might even cite Charlie's Expert Zone article, Using Input Panel
>>> During a Remote Desktop Session
>>> (http://www.microsoft.com/windowsxp/u...motedsktp.mspx)
>>> as a "method," but unacceptable work-around in every-day use.
>>> "doc jon" <docjon@discussions.microsoft.com> wrote in message
>>> news:05C116DB-D22B-4D42-B4BD-84AC7947650C@microsoft.com...
>>>> Hi, to Chris and company. I'm the doc who runs an electronic
>>>> medical records
>>>> system on Motion tablets using remote desk top with the program
>>>> running in a
>>>> thin client configuration. I last accessed the forum in September
>>>> with hopes
>>>> that there would be a fix for the handwriting recognition problem
>>>> over a network in sp2.
>>>>
>>>> -to recap, still using sp1 we can call up a floating tips panel and
>>>> its output will be recognized over the network, inputting into text
>>>> fields residing in server memory. This did not work in the
>>>> beginning, but MS quickly
>>>> supplied a server OS patch which fixed the problem.
>>>>
>>>> In sp2 the keyboard tips works, but 1. it takes up a lot of
>>>> essential screen
>>>> real estate, & 2. it stretches across the whole screen (we have to
>>>> run the program in landscape) and, as we can't seem to reformat the
>>>> tips keyboard very well, the keys are so stretched out that it
>>>> really slows down entry --
>>>> lot of side ways, back and forth tapping!
>>>>
>>>> We would like to be able to use the the hand writing recognition
>>>> engine in sp 2 as its reputedly better.
>>>>
>>>> Any inside word you knowledgeable folks have about a fix?
>>>> -- Jon

OK. My partner still has sp2 running on his Motion (and he wanted me to
revert his machine back to the set point of last August when he upgraded to
sp2 so he can get sp1 tips back again), so I'll suggest he try this tomorrow
in clinic. Jon

"Charlie Russel - MVP" wrote:

> One other point -- you need to make sure that the remote window is the
> "active" window when you insert text from handwriting.
>
> --
> Charlie.
>
> doc jon wrote:
> > Now I'm a bit unsure. It's been months since I had sp2 running on my
> > motion then uninstalled it because mentioned problems. I'm running
> > RDS/WTS; I could only use the onscreen keyboard, not the handwriting
> > recognition TIPS, as its ASCII output seemed not to be transmitted
> > into the text fields in programs running on the server. But you are
> > indicating, Charlie, that handwriting recognition does work over a
> > network? Jon
> >
> > "Charlie Russel - MVP" wrote:
> >
> >> Good point about the suggestion -- it's free, where the support case
> >> won't be. (and I would certainly agree that my column workaround is
> >> woefully inadequate at best.)
> >>
> >> --
> >> Charlie.
> >>
> >> Chris H. wrote:
> >>> As Charlie already posted, there's no solution (even a hint of one)
> >>> at this point. I would very strongly suggest filing a suggestion
> >>> with Microsoft: http://register.microsoft.com/mswish/suggestion.asp
> >>> (Use "other" in the Product: selection box) with the details. You
> >>> might even cite Charlie's Expert Zone article, Using Input Panel
> >>> During a Remote Desktop Session
> >>> (http://www.microsoft.com/windowsxp/u...motedsktp.mspx)
> >>> as a "method," but unacceptable work-around in every-day use.
> >>> "doc jon" <docjon@discussions.microsoft.com> wrote in message
> >>> news:05C116DB-D22B-4D42-B4BD-84AC7947650C@microsoft.com...
> >>>> Hi, to Chris and company. I'm the doc who runs an electronic
> >>>> medical records
> >>>> system on Motion tablets using remote desk top with the program
> >>>> running in a
> >>>> thin client configuration. I last accessed the forum in September
> >>>> with hopes
> >>>> that there would be a fix for the handwriting recognition problem
> >>>> over a network in sp2.
> >>>>
> >>>> -to recap, still using sp1 we can call up a floating tips panel and
> >>>> its output will be recognized over the network, inputting into text
> >>>> fields residing in server memory. This did not work in the
> >>>> beginning, but MS quickly
> >>>> supplied a server OS patch which fixed the problem.
> >>>>
> >>>> In sp2 the keyboard tips works, but 1. it takes up a lot of
> >>>> essential screen
> >>>> real estate, & 2. it stretches across the whole screen (we have to
> >>>> run the program in landscape) and, as we can't seem to reformat the
> >>>> tips keyboard very well, the keys are so stretched out that it
> >>>> really slows down entry --
> >>>> lot of side ways, back and forth tapping!
> >>>>
> >>>> We would like to be able to use the the hand writing recognition
> >>>> engine in sp 2 as its reputedly better.
> >>>>
> >>>> Any inside word you knowledgeable folks have about a fix?
> >>>> -- Jon
>
>
>