Custom Query (3910 matches)

;#=#INDEX#==============================================================================================================================# ;# Title .........: _Prime.au3 # ;# Description....: A collection of Prime based and Prime related mathematical operations # ;# Date ..........: 22.9.08 # ;# Author ........: jennico (jennicoattminusonlinedotde) # ;# Functions......: _IsPrime ( $s_number, $s_limit = 32000000 ) # ;# _PrimeNext ( $s_number ) # ;# _PrimePrevious ( $s_number ) # ;# _IsEven ( $s_number ) # ;# _Cross ( $s_number, $s_mode=0 ) # ;# _Factorial ( $s_number ) # ;# _gcd ( $s_number1, $s_number2 = "-", $s_number3 = "-", $s_number4 = "-", $s_number5 = "-" ) # ;# _lcm ( $s_number1, $s_number2 = "-", $s_number3 = "-", $s_number4 = "-", $s_number5 = "-" ) # ;# 1000 ( $x, $s_separator = "" ) # ;# Internal...: Euclid ( $a, $b ) # ;# _ggT ( $s_number1, $s_number2 = "", $s_number3 = "", $s_number4 = "", $s_number5 = "" ) # ;# _kgV ( $s_number1, $s_number2 = "", $s_number3 = "", $s_number4 = "", $s_number5 = "" ) # ;#======================================================================================================================================#

other languages have built in functions like _isprime, _primenext, _primeprevious, _gcd, _lcm, _factorial or _cross, which are very useful for scripting

i scripted very fast implementations of _isprime, _gcd (greatest common divisor) and _lcm(least common multiply)

all functions could be added to math.au3 or even build in.

thanks for your attention

j.

I Hope You Add Function To Get Process Path In Vista Because All Examples Work Only In XP But In Vista It Retun ? For About 90% Of All Running Proceses

This is really a two part request. I believe WinTitleMatchMode should actually be a parameter on all of the Window management functions. Why? I came across a situation that I didn't realize was happening where one of the many window titles I am working with in my script slightly changes dependent on a file being opened or the state of the app (I generally like to keep the mode on 3). Now I know you can just insert the WinTitleMatchMode function in front and behind the particular Window function you are calling in order to remedy this, but I believe it would be very convenient, clean, concise, and intuitive to just have the optional parameter extended into the window management functions. Ex. WinActivate ( "title" [, "text"[, "match = 1"]]). And it wouldn’t break anything. This way you don’t have to have a universal WinTitleMatchMode and constantly inserting it every time you need to change it. I'm making my own functions like this for the time being, but I think this would be a great help to all. The second portion of my request is to the Control functions in the window management functions. I think that control functions should follow the logic of the window function with the WinTitleMatchMode just to make things easier, and also include the WinTitleMatchMode optional parameter in them as well. All for the same reason and also to get rid of the need for WinGetTitle().