Key In commands misbehave

Key In commands misbehave

Post by murali.dha » Wed, 14 Feb 2007 05:43:54


Hello Microstation users,

I am trying to write a MDL program that would export the current model
to a parasolid (x_t) file. I am trying to accomplish this using the
following function call

mdlInput_sendSynchronizedKeyin ("mdl keyin xmt xmtout
test_parasolid.x_t",TRUE,INPUTQ_EOQ,NULL);

When I load my MDL program into Microstation and do the appropriate
actions that call the function containing this line, I do see a
'Export to Parasolid-XMT file' message on the Microstation status bar,
but no file is written. I tried giving the full path to the file like
C:\tmp\test_parasolid.x_t and still no file is written. On the other
hand when I do a

mdlInput_sendSynchronizedKeyin ("mdl keyin xmt
xmtout",TRUE,INPUTQ_EOQ,NULL);

I see that the Export Parasolid dialog box pops up and prompts me for
a location to save the file. Also, when I key-in xmtout C:\tmp
\test_parasolid.x_t in the Key-in dialog of Microstation, the file
gets written and location dialog does not show up (as expected)

I am not really sure what I am missing in the above command. Any help
will be greatly appreciated.

Thanks,
Murali Dhanakoti
Software Engineer, ESI CFD Inc.
6767 Old Madison Pike, Ste 600,
Huntsville, AL 35806
 
 
 

1. Right arrow key MISBEHAVING in EXCEL

2. MountedDevices key: Misbehaving drive letters

I've got a multiboot system with Win 2000 SP4 on each.

REcently, I decided to add Linux, so I repartitioned two USB drives as
follows:


USB-1: Logical drive O (NTFS), followed by a Linux ext3
USB-2: Logical drive P (NTFS), followed by a Linux Swap partition.

On all but 1 of the OS, the drive letters are as desired, but on one:

1. Looking at My Computer, S is also assigned to the P drive.
2. Looking at Disk Management, only the S is shown.

Is it safe to take the HKLM\System\MountedDevices key from one of the
properly behaving OS, and import into the misbehaving OS?

Or do those keys get automatically reconfigured each time I reboot?

If not, how do I fix this?

The difference between the misbehaving OS and the others is the misbehaving
OS was installed OVER Win 98, whilst the others were clean installs.

3. Further to Down Arrow key misbehaving?

4. Command prompt misbehaving

5. Tab key misbehaving

6. Gray Arrow Keys Misbehaving When Num Lock is On

7. home key misbehaving

8. Return Key misbehaving

9. Tab Key misbehaving

10. Help: Command Prompt code misbehaving in VBS

11. Command Prompt code misbehaving in VBS

12. Down Arrow key misbehaving?

13. move command misbehaving in win2k server

14. Misbehaving sort command in unix

15. Tab key misbehaves