Hi everybody!

We are working with Dragon (DMPE 2.3.1 / 3.2) since years and it works pretty good.

Our main target program  is a radiologic information system (RIS) from NEXUS.

Adding this line into nsapps.ini

Tx28_Dotnet=10

Dragon has full text control with Select-and-Say in the 32 Bit edition - but is totally lost in the 64 Bit edition! The new release of the RIS is 32 bit discontinuated - only 64 bit!!

So we running in a big problem...

DMPE 4 has got the same problem and DMO is a not acceptable!!!

Has anyone got a solution or an idea???

 

If you don't want to go with DMO, which we are not certain would even work for your needs, your only option is to plead your case with NEXUS. Of course NEXUS is unlikely to listen to you considering that Nuance no longer supports any Dragon Medical utilities other than DMO. However, you might be able to convince them to temporarily continue offering their 32-bit legacy release; perhaps with no support. We appreciate that you are between a rock and hard place

 

Our rant (not to be taken too seriously):

 

Nuance's general third-party development rule is that other application manufacturers need to bend a knee to Nuance and not the other way around. We generally like this attitude and believe all software manufacturers should wake up and pay more attention to what the public actually wants. Typing became antiquated around the turn-of-the-century. It's time for all major software manufacturers to make their applications Dragon friendly. Microsoft even offers complementary tools. Software manufacturers who continue to ignore Microsoft/Nuance's speech recognition may find themselves left behind by their competition.

Possible solution:

If you can move up to DMPE 4.3.1, assuming you can find it, you should be able to directly dictate with DragonCapture, as opposed to having to cut and paste from Dragon's Dictation Box or another utility. Unfortunately, there is probably no way to reenable Select-&-Say. You'll find a 30 day trial in our signature tag 

-------------------------

Change "No" to "Know" w/KnowBrainer 2022
Trial Downloads
Dragon/Sales@KnowBrainer.com 
(615) 884-4558 ex 1

 

I'm not sure if I heard anyone use 64bit TxText controls with Dragon successfully, but most of the time when Dragon wouldn't support Full Text Control it was simply because of a new TxText version.

 

With the line above you've told Dragon to treat windows with Tx28_Dotnet (in their) window class as TxText controls (10).

Could it be that Nexus has updated their TxText control version with the previous release and that this is the root cause why it doesn't work anymore?

 

Please check (with Spy++ or WinSpy, for example) what the target window's Window Class is.

Only after you've made sure that the current 64bit version is actually also using TxText v28 we can infer that 64bit TxText v28 is not compatible.

The most current version of TxText is 31, so chances are Nexus simply performed an update and is no longer using 28.

 

hth

mav

Thank you Lunis and Mav - it feels so good to get replies on your problem!!

@Lunis
As you know DMPE is discontinued...

@Mav
NEXUS says that there is the same TxControl 28 runnig...

 

First rule of any support: Don't believe anything the user says unless you have verified the claim!

 

Have you verified what the exact WindowClass for the editor you're trying to use is?

 

With TxText Control's creative way of setting their window class names I wouldn't be surprised if their 32bit and 64bit components used different class names...

 

hth

mav

[General]
Handle: 0x610902

Class: WindowsForms10.TX28_DOTNET.app.0.289b16d_r6_ad1
ClassNN: WindowsForms10.TX28_DOTNET.app.0.289b16d_r6_ad11
Style: 0x54310000
Extended: 0x00000000
Position: 0, 0 (836, 259)
Size: 1058 x 678 (1039 x 659)
Cursor: 1171, 540

Looks like it actually _is_ a TxText control for .NET Windows Forms v28, so we can rule out a version mismatch. Thanks for checking.

 

Luckily, I still have a V31 trial version hanging around and while it has expired in the meantime, the Demo application contained is still working and it is 64bit!

I've added

TX31_DOTNET=10

to the

[\Enable Class Names]

section in nsapps.ini in %PROGRAMDATA%\Nuance\NaturallySpeaking16

and got full text control in the 64bit TxText control:

I appreciate your help so much!!!

I checked everything. -> OK

Do you have more ideas?

Hmmm - the only thing I can think of is some setting in %appdata%\Nuance\NaturallySpeaking15\nsuser.ini.

Can you find anything regarding your EMR's executable name there?

Dragon can create sections in the form

[ExecutableName|Version\Compatibility Module Status]

to turn on/off compat modules specifically for certain applications.

 

In addition, there's a section

[.Global\Compatibility Module Status]

for all other applications not mentioned explicitely.

 

Mine looks like this:

 

[.Global\Compatibility Module Status]

MyCommands=1

Natural Language Commands=1

Tracking=1

Edit Control Support=1

MS Excel=1

OOWriter=1

MS Word=1

Corel Word Perfect=1

Global Dictation=1

 

Apart from that I can only suggest to create a new user and/or to remove the nsuser.ini file and try if it works now.

 

hth

mav

Looking at the amount of views it seems to be a frequent problem...

I am wondering that Nuance does not react at all -- in my eyes a lack of confidence in this company!!!

In Germany we say: Also other mothers have pretty daughters!!!

In times of Cortana, Google, Alexa, etc. Nuance should awake from sleeping!!

Other opinions welcome