|
|
Post by tomyuhas on Oct 5, 2020 22:21:39 GMT 1
New exe corrects the Shift+Arrow number pad problem. WP Shell Screen Captures cannot be pasted to C Prompt screen selected by pressing "1" at shell menu screen  WPShell Screen Captures can be added to C prompt if I use G menu item - Go To DOS for One Command option  |
|
|
|
Post by Jos on Oct 5, 2020 22:37:07 GMT 1
You have to help me out: What does the "Shell screen capture" mean at all?
25 lines x 80 columns = 4,000 characters are copied to an internal buffer?
Then pasted into the 16 bytes BIOS keyboard buffer. Wouldn't work in DOS or NTVDM.
And no, you cannot paste images to a DOS program. Only text that is pushed into the BIOS keyboard buffer.
Jos
|
|
|
|
Post by tomyuhas on Oct 10, 2020 18:59:20 GMT 1
The new version fixed DP's Shft+NumPadArrow movement. Thank you. However, Shell "Go To DOS" command remains a problem in that the CMD Line prompt will not allow screen pastes into the CMD line or any other screen capture and past actions so long as the command line is shown. Even the F7 exit does not work. The only way to return to shell from "Go To DOS" is by typing Escape. Since I use Macros to open files referenced in the DP Data Fields, this is a bit of a problem. A "work around" is available by using Shell's "Go To DOS for One Command" Menu Item "G". At the "DOS Command" prompt users need to know to type: CMD /C "path\filename.doc" to start a doc or pdf file. Finally, another vDos problem for DPMouse users is an error and forced exit occurs if DPMouse is used to trigger a Shell Macro. In the screenshot below, I used DPMOUSE click on [<ViewIC3>] to start a macro that is suppose to open PDF file IC306076 which is the Invoice referenced for ambulance transport. The error "Program Tried To Resize MCB Block 0" appeared and forced Shell to close. I wonder if that can be fixed?  Thank you for your work. |
|
|
|
Post by emendelson on Oct 10, 2020 20:43:39 GMT 1
Hello Tom,
Just to clarify this. I think I can reproduce part of your report by doing this.
1. Start Shell.
2. Choose 1 - Go to DOS.
3. At the DOS prompt, I CAN paste the Windows clipboard by using the Win-Ctrl-Shift-V keystroke or the vDos System Menu Paste Clipboard
Text item. I *think* this is NOT the problem that you are describing. Instead, (a) you are running a Shell macro, and (b) you are trying to use the Shell macro command that pastes the Shell clipboard (not the Windows clipboard) at the cursor position.
I don't have a WP Office Reference here, so I don't remember the exact command. But if you could spell out exactly - in full step-by-step detail - what you are trying to do, that would be a help. It would also help if you could create a simple Shell macro that would copy text from (for example) WPDOS 5.1 and try to paste it at the cursor position in a Shell Go-to-DOS prompt, that would make this easier to test.
If I'm wrong, just say so and I'll remove this message.
|
|
|
|
Post by tomyuhas on Oct 10, 2020 22:27:23 GMT 1
Ed,
You are correct -- I am trying to paste Shell Clipboard item into Shell's "Go To DOS" command line and it cannot be done. This problem does have a work around -- for some reason that I'll never understand, Shell Menu item (out of the box menu Shell.fil file) has a "G" selection named "Go To DOS for One Command". Incredibly, if I use that "G" option, I can paste Shell Clipboard into that Command Line -- I need to use CMD /C in front of "path\filename.pdf", but it will work. Problem is I need to rewrite all of my macros -- which I'd be happy to do except macros are triggered by a DPMouse function that does not work correctly -- it errors out with message that DPMouse "Program tried to resize MCB block 0".
The inability to paste Shell screen capture into "Go To DOS" line is the same for any program -- shell clipboard stops working once "1" Go To DOS is selected and remains off (cannot paste, cannot capture) until F7 or "Exit" closes the line "(shell) c:\office30>" prompt. I can type at the prompt, I just cannot use shell screen capture clipboard any time that command line is activated.
Again, problem can be worked around using alternative "G" Go To DOS for One Command".
Tom
|
|
|
|
Post by emendelson on Oct 10, 2020 22:43:54 GMT 1
Jos and Tom, I've figured out how to illustrate what Tom is asking about.
In DOSBox or NTVDM, you can do this:
1. Start Shell.
2. Start WordPerfect and type some text.
3. Press Shift-Alt-minus to start Screen Copy Mode.
4. Choose 1 Rectangle; move the cursor to the start of the text you want to copy; press Enter; move the cursor to the end of the text you want to copy; press Enter.
5. At the Clipboard menu, choose 1 Save.
6. If you are in the Shell, choose 1 Go to DOS.
7. At the DOS prompt, you SHOULD be able to press Shift-Alt-plus to paste in the text in the Clipboard. In vDos, this does nothing. It works correctly in DOSBox or NTVDM.
8. Type Exit to return to the Shell, choose G Go to DOS for One Command.
9. At the prompt, press Shift-Alt-plus. The copied text is pasted correctly.
|
|
|
|
Post by Jos on Oct 11, 2020 0:28:18 GMT 1
Don’t think this is actually a problem, you can use Win+Ctrl+Right mouse click to select and copy text (to the Windows clipboard). That will be quicker than the Shift-Alt-minus method. And would let you paste the copied text at the command prompt with Win+Ctrl+Left mouse click.
As WP or DP shells out to the DOS command processor/prompt, it’s no longer in control of the (user) input. It will leave some portion of its code resident to for instance paste text. Would be by redirecting INT 9, that doesn’t work in vDos.
I don’t know about the macro’s Tom is using, and perhaps should have a closer look at ‘starting’ non-executables if the DOS programs uses the roundabout of command shell to invoke those. Like opening a PDF document.
Tom got a prerelease of the next vDos version. That has unfinished work to extend the Windows Clipboard copy function. Win+Ctrl+Right mouse click should then give you more options. Enabled with “COPYCLIP = LPTx/COMx” in config.txt. Where LPTx/COMx = … defines what should be done with the Clipboard (exported to LPTx/COMx.asc/txt). I however don’t know if that would accommodate Tom and its macros.
Jos
|
|
|
|
Post by emendelson on Oct 11, 2020 0:43:10 GMT 1
The reason that Tom (I think) can't use Win-Ctrl-Right click is that he's using Shell macros that perform the equivalent of Shift-Alt-plus to copy text into a command prompt. What Tom says about Shell macros seems to mean that the Shell Macro command takes text from the DP screen and then types it into the command prompt. The steps I used were simply to illustrate the problem that also occurs in macros.
Shell Macros are extremely powerful - they can copy bits of the screen, no matter what program is running, and use the copied text anywhere else. This is different from using keystrokes to manage the Windows clipboard.
|
|
|
|
Post by Jos on Oct 11, 2020 12:07:42 GMT 1
Problem will be that the resident part of WP Shell will use INT 9 to detect F7 or Shift-Alt-plus, manual user input.
DPmouse and the "Program Tried To Resize MCB Block 0" error seems odd. DPmouse is a TSR program, already running. But the screenshot shows “DPmouse v 2.3 Copyright…” overwriting the DP text. That would indicate DPmouse is started once more, now from within an already running program (DP)?
Jos
|
|
|
|
Post by emendelson on Oct 11, 2020 13:58:54 GMT 1
One question: when a Shell macro uses its "write clipboard" (or whatever the exact name is) command to write the contents of the clipboard, would it also use INT 9? It makes sense that the problem with the keyboard is caused by INT 9, but does this also apply to Tom's shell macros?
And to clarify this for Tom: vDos does not support INT 9, which is used by very few DOS programs to get keyboard input.
|
|
|
|
Post by Jos on Oct 11, 2020 16:20:10 GMT 1
No, INT 9 would only be used to detect keyboard input while WP Shell doesn’t have the ‘focus’.
Jos
|
|
|
|
Post by tomyuhas on Oct 11, 2020 17:29:49 GMT 1
Ed and Jos,
Thank you for your efforts.
Ed is correct, the Shell Marcos I use from inside DP grabs various text from within DP screen and then uses Go To DOS to launch pdf (and other file types) so users can view and/or capture PDF file data to Windows Clipboard to drop it into DP fields.
I can launch a Shell Macro by using Shft_Alt+F10 and then typing in the Macro Name -- that part works using VDos, but only if I use the "G" Menu alternative "Go To DOS for One Command" Shell menu item and type cmc c/ "path\filename.pdf". It does not work using "1" "Go To Shell" menu option which does not normally (not using vDos) require that I include the cmd /c preface to launch a file.
DPMouse allows one click macro launching. If I click on any macro name enclosed in twin brackets [<MacroName>], DPMouse captures then MacroName and apparenly does the Shift+Alt+F10 keystrokes to start the Macro. So, to sum up, VDos will do keystroke entered shell macro lauches to "G" Menu Go To Dos for One Command but will not allow screeen captures to be deposited at the "1" Go To Shell command line -- it also freezes if I attempt to use DPMOuse one click to launch a ShellMacro.
Jos is correct that DPMouse does appear to be trying to restart itself because the copyright text is superimposed on top of the DP screen text -- no DP data is touched in the process, but Shell closes along with DP and DPMouse.
DPMouse is not a stand alone product. It is an exe that requires DP.exe and DP.Sys be in the same directory to work. Multiple network users can have DP sessions going at the same time using just one network folder containing a single copy of DP and DPMouse.
That is as much information as I can supply.
Once again, thank you for your continuing efforts.
Tom Yuhas
|
|
|
|
Post by emendelson on Oct 11, 2020 18:09:46 GMT 1
No, INT 9 would only be used to detect keyboard input while WP Shell doesn’t have the ‘focus’. So that means that Tom's shell macros should work correctly, but Tom, this can't be tested without a simple macro to work with. |
|
|
|
Post by emendelson on Oct 11, 2020 18:12:23 GMT 1
I can launch a Shell Macro by using Shft_Alt+F10 and then typing in the Macro Name -- that part works using VDos, but only if I use the "G" Menu alternative "Go To DOS for One Command" Shell menu item and type cmc c/ "path\filename.pdf". It does not work using "1" "Go To Shell" menu option which does not normally (not using vDos) require that I include the cmd /c preface to launch a file. Tom, I don't understand this, unfortunately. You say that you can type in a Macro Name, but then you say you type "cmd /c path\filename.pdf" - but a PDF is not a Shell Macro. Could you expand this so that we know exactly what works and what doesn't work? |
|
|
|
Post by tomyuhas on Oct 11, 2020 18:38:28 GMT 1
Ed,
Shell Macro named "ViewKC" -- in 32bit Dos, I use DPmouse click on [<ViewKC3>] to launch the macro. With vDos, I need to use manual input to start macro.
Manual start: I use Shft+Alt+F10 and then type "ViewKC"+Enter -- Macro begins the sequence dictated by SHM file name ViewKC3.
First, Macro begins by inputting keystrokes that capture text from various parts of DP Screen. Text captures (as many as 10 using Macro Variables 0-9) are stored in Shell Macro Variables. Once Macro has gathered all of the data it needs to feed to command prompt (Case name, Case Number, File name) it then does keystrokes Contr+F1+1 to display Shell Menu Screen.
At this point my old Macro will feed in "1" Go To DOS and if vDos is operating, the Macro freezes because VDos does not allow Macro Variable to be pasted at the C Prompt.
New Macro that I have created for vDos and a work around, uses Shell Menu Opiton "G" "Go To DOS for One Command" which does allow macro to feed screen captures in at dos prompt and works, but only if macro now has CMD /C before "path\filename".
Sorry for the confusion -- it is due to the fact that I was referring to two different Macros -- one built on 32bit system that allow screen captures to be pasted at (Shell) "C Prompt" and the other macro necessitated by vDos's prohibition of screen pastes at that prompt.
In vDos, all of my old macros stop when they get to c:\ prompt.
So, I built new macros that use "G" Shell Menu item which is Go To DOS For One Command.
New macro does everything the same as old macro up until it needs the command prompt -- new macro chooses G option and then feeds in CMD /C followed by path and filename information from DP screen captures.
So, I have a work around but need to rebuild the old Macros to work using the G Menu option instead of the "1" Go To DOS option.
Is that somewhat clearer?
Tom
|
|
