DosTips.com

VooDooGuito wrote: ↑

02 Jun 2020 11:02

Hi dudes, there are a way to use transparency 100 without cover the prompt?

No that won’t work, the transparency affects every part of the cmd window, text included.

Thanks to both of you!

Release of version 1.5 (link in first post) What's new: 1. The sendkey operation now allows sending an entire "string" instead of a single virtual key code. This makes it a lot easier to use. For example,in the example script automation-cmdwiz.bat : ::Previous: cmdwiz sendkey 0x10 d & cmdwiz sendke...

Here is a crude estimation of atan, based on the second answer at https://math.stackexchange.com/questions/1098487/atan2-faster-approximation . I also had to handle the case where y is 0. This could be improved upon in many ways, but it is acceptable for what I needed it for. @echo off rem Calculate...

Anybody happen to be sitting on an atan or atan2 batch macro? This is the best I got at the moment: atan2.js: WScript.Echo(Math.floor(Math.atan2(WScript.Arguments.Item(0),WScript.Arguments.Item(1))/Math.PI*180)) batch script: cscript //nologo //e:javascript "atan2.js" !TXE! !TZE! >res.txt set /p ERY...

VoodoGuito: Without the use of any exes, or only with exes that come packaged with Windows? Pretty much any command you run is an ”exe”, you know... Anyway, since you probably mean ”without external exes”, the answer is: yes, you can. That’s not the topic here though, I suggest starting a new thread...

Thanks. I'm willing to bet you have a scale setting (in your Windows Display settings) set to something larger than 100%. Apparently Cmwiz doesn't take this into account. I will add it to the list of Cmdwiz bugs to fix.

EDIT: now fixed in Cmdwiz 1.5

Fullscreen at 1360 * 768 pixels (Native resolution is 3840 * 2160, at which only approx 1/6th of the cmd window is occupied by cmdgfx_gdi's output) hmm, that’s a bit puzzling. 3840*2160 (8 million pixels) is admittedly a much larger screen than I ever tried cmdgfx with (max I tried is probably 1920...

Liking the color by state expession. I'm getting approximately 18 frames per second for the latest version compared to the ~110 from your original version. I actually prefer that pace as it's easier to see the evolution between generations. Did have to lower my screen res to scale it to full screen...

Optimization attempt: The general rule for expressions is simple: the longer they are, the slower they run. At a granularity of ~2 million pixels, it might be worth trying to cut it a bit. By only allowing using color 1, we can get rid of 9 calls to gtr, plus the final multiplication. But isn't that...

try doing the same in pixel mode and it wouldn't be so pretty... Actually let's try it: @echo off setlocal EnableDelayedExpansion cmdwiz fullscreen 1 & cmdwiz showcursor 0 cmdwiz getdisplaydim w & set /a w=!errorlevel! cmdwiz getdisplaydim h & set /a h=!errorlevel! set /a density=10, col=10 if not ...

Mmmm... I am confused... If I correctly understood, your long expression count the neighbours of one pixel , store it in s0 storage variable (there are just 5 storage variables) and this variable is used to know the final value of the pixel. However, your description did not explain what to do with...

Does the cmd window just seem to hang, no input or output?

It did for me, try enabling legacy console mode in cmd preferences.

Can't yet claim to understand how the rules of Game of life are being implemented in the script Things do tend to get cryptic when having to compose everything in a single line :mrgreen: (not true, it could be broken into several lines, but i digress) Actually, it's worth a break-down. Entire expre...

I may just have to start learning how to utilise cmdgfx Please do if you feel like it, would be fun to see what you could do with it. It is fairly well documented, both from command line and at https://github.com/misol1/cmdgfx/blob/master/README.md Then again, it is quite a feature-rich program (so...