DosTips.com

Can you explain what you did here? :: set /a "%4.MIN3=-((%22-%11)>>32)*(-((%33-%22)>>32)*%3 - ((%22-%33)>>32)*%2) - ((%11-%22)>>32)*(-((%33-%11)>>32)*%3 - ((%11-%33)>>32)*%1)" :: set /a "%4.MAX3=-((%22-%11)>>32)*(-((%33-%11)>>32)*%1 - ((%11-%33)>>32)*%3) - ((%11-%22)>>32)*(-((%33-%22)>>32)*%2 - ((%...

As said above, i assumed linear distances of the colors in RGB-space: The main advantage is, it is easy to compute, because color distances are just euclidean distances over the coordinates of the RGB colors. The main issue is, that human perception of color is everything but linear. Typically that ...

I've replaced the grayscale algorithm, the (unoptimized - but hopefully bug-free) result is the following mapping function: :toColorTable R G B return var :: part 1 (sloppy is sufficient) set /a "%4.r1= -(-(%1>>6)>>2), %4.g1= -(-(%2>>6)>>2), %4.b1= -(-(%3>>6)>>2), %4.isDarkGray=%4.r1*%4.g1*%4.b1" se...

Ok, i somehow missed the fact, that the difference between 0 and 95 isn't 40... :oops: . Your solution already finds the best color match; however this is my try: :: color function style set /A "%4=(((%1)-35)/40+((%1-48)>>8)-((%1-74)>>8))*36 + (((%2)-35)/40+((%2-48)>>8)-((%2-74)>>8))*6 + (((%3)-35)/...

I'm not sure what you mean, the above computations should return an index (i) for the indexed color (r_i, g_i, b_i) with the minimal error to the given color value (r, g, b) - at least for any system, that uses the above colour table predefined by Microsoft: - The formular for (2) should return the ...

The color map (at least on my pc) is piecewise linear. 1) Indices 0x00 - 0x0F contain the most non-linear part: ( 0, 0, 0), (128, 0, 0), ( 0, 128, 0), (128, 128, 0), ( 0, 0, 128), (128, 0, 128), ( 0, 128, 128), (192, 192, 192), (128, 128, 128), (255, 0, 0), ( 0, 255, 0), (255, 255, 0), ( 0, 0, 255),...

I assume the error is caused by using the wrong environment variable named "Aufruf:" instead of "Aufruf", like you did in "Linie2.bat":
penpen

If i remember correct, then you can find those in the Templates for Parallax zip-file IcarusLives linked somewhere above, but under a diffferent name:
- "template1.ppm" is "cloud1.ppm"
- "template2.ppm" is "mountain1.ppm"
- "template3.ppm"should contain another mountain version.


penpen

The following might help you: Though i would add debug messages (using echo) and pauses, to see the program flow.
In case you don't have a visible console on login, you might redirect the echoes and avoid the pause commands instead.


penpen

I actually can't test it, but it might be the space characters, that break the value early, so you might encapsulate the value "c:\Program Files\Common Files\Corel\" in doublequotes.

penpen

What you see there is a character encoding issue. Somehow the resulting file was created with the byte order mark (bom) of 'UTF-16 LE' (which could happen for various reasons). Then the reg file was appended. Save the text into a file using encoding 'UTF-16 LE'. Then open it within a hex-editor. Del...

In case your computer runs on the "pro", "enterprise" or "educational" version of windows 10 (probably the same under Windows 11), then you may use "msg" or "net send ..." commands to send messages to computers in your local network: msg /SERVER:DestinationPC * /TIME:60 "Sample message to pc 'Destin...

Though i like Aacini's version, it is not completely safe (for example if you change the codepage of the source-xml).
Here is an example for how to read and process xml using jscript (in the hybrid "xslt.bat") in a safe way:
viewtopic.php?p=32941#p32941.

Is there information about why FOR treats space characters as commands instead of ignoring them? It deviates from default behavior imo. It is the default behaviour: If you escape a character (using the circumflex-character '^'), or add characters when the interpreter expects text starting with esca...

That's not "nothing" - it's a space-character. Since the space-character is no valid command, the error message is correct. Typically space characters are treated as whitespace characters and will not end up beeing treated as a command. But you can force cmd to treat the space-character as a command...