Text Only | Text with Attachments

QB64.org Forum

Active Forums => QB64 Discussion => Topic started by: doppler on October 06, 2020, 01:50:47 pm

Title: Opinion, insite, idea's wanted for shell out pass back through the clipboard
Post by: doppler on October 06, 2020, 01:50:47 pm
Basically I am looking for a better way to pass back clipboard content from a shell out.

Start with: "shell "dir *.* | clip", not what I am going to do.  But you get the idea.  What comes back is line by line content in the clipboard where the lines are separated  by (cr/lf).   ie:line1(cr/lf)line2(cr/lf),line3(cr/lf)....

I can only think of "a$=_clipboard$" then using instr a$ taking the lines content with mid$'s.  Tedious and time consuming.  An alternate way would be shell "dir *.* > somefile.txt" and reading the file back with line inputs.  Also time consuming.

All input and out devices are considered block devices on windows.  Some are read only (keyboard), some are r/w (display).  The clip board is no different to windows.  And its a block device that is r/w.  The open command does not support many block devices in QB64.  So the question is the clipboard a "open-able" device on windows.  And how to do it?  I happen to be using the alternate way now.


Title: Re: Opinion, insite, idea's wanted for shell out pass back through the clipboard
Post by: SpriggsySpriggs on October 06, 2020, 01:56:44 pm
I'd say if you aren't wanting to split everything up line by line or read in contents (which I think is quite quick in most scenarios I've dealt with) then you should look at this:
https://docs.microsoft.com/en-us/windows/win32/dataxchg/clipboard-functions (https://docs.microsoft.com/en-us/windows/win32/dataxchg/clipboard-functions)

I can't guarantee that this will work for you. I haven't looked at this portion of the WinAPI yet.
Title: Re: Opinion, insite, idea's wanted for shell out pass back through the clipboard
Post by: doppler on October 06, 2020, 02:16:00 pm
Yea, I saw that on google search results.  Using the windows api's are not the easiest things to do inside qb64.  I played a long time ago the string method, it was very slow and complex.  That's why I went with file re-direction method.  A really long time ago, when qb45 was still king.  I saw and used a way to take clipboard content and directly pump it in to an array using pointers and such.  This is not the dos age anymore.  So that nice way is gone now.  Unless memory arrays can be directly adjusted in QB64 ????

Title: Re: Opinion, insite, idea's wanted for shell out pass back through the clipboard
Post by: SpriggsySpriggs on October 06, 2020, 02:22:30 pm
Quote from: doppler on October 06, 2020, 02:16:00 pm
Using the windows api's are not the easiest things to do inside qb64.

Trust me, they're not as hard as you think. I'll try messing with it myself here and reply with source code if it is successful.
Title: Re: Opinion, insite, idea's wanted for shell out pass back through the clipboard
Post by: Pete on October 06, 2020, 02:36:40 pm
I don't think I understand the question. Your piping example works.

If I use... SHELL "dir /b C:\tmp-copy-qb64bas\*.wav | clip": PRINT _CLIPBOARD$

Results:
----------------------------------
recording.wav

test1.wav
----------------------------------

The same results would be given if I sent the results to a file...  "dir /b C:\tmp-copy-qb64bas\*.wav>junk.txt"

If I want to remove the print characters like carriage return, I think the only way to do so is to parse them out where a$ = _clipboard$ and then parse a$.

Code: QB64: [Select]
  1. OPEN "junk.txt" FOR BINARY AS #1
  2. a$ = SPACE$(LOF(1))
  3. GET #1, 1, a$
  5.  
  6. DO WHILE INSTR(a$, CHR$(13) + CHR$(10))
  7.     a$ = MID$(a$, 1, INSTR(a$, CHR$(13) + CHR$(10)) - 1) + MID$(a$, INSTR(a$, CHR$(13) + CHR$(10)) + 2)
  9.  
  12.  

or...

Code: QB64: [Select]
  1. SHELL "dir /b C:\tmp-copy-qb64bas\*.htm* | clip"
  3.  
  4. DO WHILE INSTR(a$, CHR$(13) + CHR$(10))
  5.     a$ = MID$(a$, 1, INSTR(a$, CHR$(13) + CHR$(10)) - 1) + MID$(a$, INSTR(a$, CHR$(13) + CHR$(10)) + 2)

Results for either:

----------------------------------
recording.wavtest1.wav
----------------------------------

Is that your intended results?

Pete
Title: Re: Opinion, insite, idea's wanted for shell out pass back through the clipboard
Post by: doppler on October 06, 2020, 02:55:32 pm
My original idea is I need a list of files quickly from a directory passed back to my qb64 program.  Output re-direction is messy and leaves behind file(s) that need to be cleaned up later.  I thought the clipboard being ram would be faster than opening a list from a re-directed output.  The clipboard leads to special handling of a string to parse out the needed content.  If the clipboard was an open-able device I could use an "line input" to take the lines out of the clipboard one by one since (cr/lf) is the delimiter for line input.

I am just thinking about a more elegant way of doing it.  Doing the mid$ thing seems clunky (maybe the only real way).  I know the piping works, I was looking for a "elegant,generic" way of getting the data.
Title: Re: Opinion, insite, idea's wanted for shell out pass back through the clipboard
Post by: jack on October 06, 2020, 03:00:07 pm
how about using the WinAPI FindFirstFile, FindNextFile and FindClose ? https://stackoverflow.com/questions/612097/how-can-i-get-the-list-of-files-in-a-directory-using-c-or-c
Title: Re: Opinion, insite, idea's wanted for shell out pass back through the clipboard
Post by: doppler on October 06, 2020, 03:04:37 pm
Quote from: jack on October 06, 2020, 03:00:07 pm
WinAPI FindFirstFile, FindNextFile and FindClose
I thought of that one.  Since there is a program here already:
Code: QB64: [Select]
  2.     FUNCTION load_dir& (s AS STRING)
  3.     FUNCTION has_next_entry& ()
  4.     SUB close_dir ()
  5.     SUB get_next_entry (s AS STRING, flags AS LONG, file_size AS LONG)
  7.  
  8. REDIM Dir(0) AS STRING, File(0) AS STRING
  9.  
  10. 'D$ = _CWD$
  11. D$ = "D:\mangadex"
  12. GetFileList D$, Dir(), File()
  13.  
  14. PRINT "SUBDIRECTORIES"; UBOUND(dir)
  15. FOR i = 1 TO UBOUND(dir)
  16.     PRINT Dir(i),
  21.  
  22. PRINT "FILES"; UBOUND(file): PRINT: PRINT
  24. FOR i = 1 TO UBOUND(file)
  25.     PRINT File(i),
  28.  
  29. SUB GetFileList (SearchDirectory AS STRING, DirList() AS STRING, FileList() AS STRING)
  30.     CONST IS_DIR = 1
  31.     CONST IS_FILE = 2
  32.     DIM flags AS LONG, file_size AS LONG
  33.  
  34.     REDIM _PRESERVE DirList(100), FileList(100)
  35.     DirCount = 0: FileCount = 0
  36.  
  37.     IF load_dir(SearchDirectory) THEN
  38.         DO
  39.             length = has_next_entry
  40.             IF length > -1 THEN
  41.                 nam$ = SPACE$(length)
  42.                 get_next_entry nam$, flags, file_size
  43.                 IF (flags AND IS_DIR) OR _DIREXISTS(SearchDirectory + nam$) THEN
  44.                     DirCount = DirCount + 1
  45.                     IF DirCount > UBOUND(DirList) THEN REDIM _PRESERVE DirList(UBOUND(DirList) + 100)
  46.                     DirList(DirCount) = nam$
  47.                 ELSEIF (flags AND IS_FILE) OR _FILEEXISTS(SearchDirectory + nam$) THEN
  48.                     FileCount = FileCount + 1
  49.                     IF FileCount > UBOUND(filelist) THEN REDIM _PRESERVE FileList(UBOUND(filelist) + 100)
  50.                     FileList(FileCount) = nam$
  51.                 END IF
  52.             END IF
  53.         LOOP UNTIL length = -1
  54.         close_dir
  55.     ELSE
  56.     END IF
  57.     REDIM _PRESERVE DirList(DirCount)
  58.     REDIM _PRESERVE FileList(FileCount)
  60.  
  61.  

But redirect and read back would be faster.
Title: Re: Opinion, insite, idea's wanted for shell out pass back through the clipboard
Post by: SpriggsySpriggs on October 06, 2020, 03:28:58 pm
Doppler, I'm away from home right now but I've got the clipboard API almost done being written. Also, for the FindNextFile, there is a post from 2018, I think, that does what Pete mentioned. I downloaded the code and was going to put it in my API collection (with credit, of course).
Text Only | Text with Attachments