+- QB64 Phoenix Edition (https://qb64phoenix.com/forum)
+-- Forum: QB64 Rising (https://qb64phoenix.com/forum/forumdisplay.php?fid=1)
+--- Forum: Code and Stuff (https://qb64phoenix.com/forum/forumdisplay.php?fid=3)
+---- Forum: Works in Progress (https://qb64phoenix.com/forum/forumdisplay.php?fid=9)
+---- Thread: Text Previewer (windows only) (/showthread.php?tid=2527)
Pages:
1
2
RE: Text Previewer (windows only) - SMcNeill - 03-18-2024
Updated (Thanks to RhoSigma's suggestion) to include toggles for the various PrintModes.
RE: Text Previewer (windows only) - Pete - 03-25-2024
All I got out of this was Steve broke SHELL. When will that be fixed? Please don't go using chewing gum and twins... I mean twine.
Pete
- I always look good in text.
RE: Text Previewer (windows only) - SpriggsySpriggs - 03-25-2024
There have always been issues with SHELL in CONSOLE:ONLY vs regular window. I've just accepted them and found ways around them.
RE: Text Previewer (windows only) - mdijkens - 03-25-2024
(03-17-2024, 07:16 PM)SMcNeill Wrote: SHELL is broken.Run into this a lot.
Try these three examples:
Code: (Select All)$Console:Only
Shell _Hide "reg query " + Chr$(34) + "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts" + Chr$(34) + " /s > temp.txt"
Code: (Select All)$Console:Only
Shell "reg query " + Chr$(34) + "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts" + Chr$(34) + " /s > temp.txt"
Code: (Select All)Shell "reg query " + Chr$(34) + "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts" + Chr$(34) + " /s > temp.txt"
$CONSOLE:ONLY and SHELL works.
$CONSOLE:ONLY and SHELL HIDE doesn't work.
SHELL withotu $CONSOLE:ONLY doesn't work.
/SIGH
If it does not work, try adding "cmd /c " in front of your command
That fixes is 99% of the time
Code: (Select All)
$Console:Only
Shell _Hide "cmd /c reg query " + Chr$(34) + "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts" + Chr$(34) + " /s > temp.txt"RE: Text Previewer (windows only) - SMcNeill - 03-25-2024
The only 100% workaround that I've found is just to write the shell command into a batch file and then call it from there. Crazy, but it is what it is.
I found another SHELL that was almost impossible to deciper the other day. It was something like:
foo print 123 > text.txt
From the command line, it worked with no isses.
From SHELL, it ended up having to be something like:
SHELL chr$(34) + "powershell 'foo print 123' > text.txt" + CHR$(34)
The entire powershell command had to be listed inside the single quotes, so it'd process as a single command, and then *everything* had to be encased in quotes so that CMD wouldn't break it apart into multiple, fractional calls to crap.
Lord, the hoops to ump throug, for something so simple!!