Changeset 242 for trunk/SRC/Utilities
- Timestamp:
- 04/06/07 10:35:17 (17 years ago)
- Location:
- trunk/SRC/Utilities
- Files:
-
- 15 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/SRC/Utilities/createfunc.pro
r239 r242 5 5 ; useful to avoid the use of execute 6 6 ; 7 ; @param command {in}{required} 8 ; a scalar stringdefining the result to be given back by the function.7 ; @param command {in}{required} {type=scalar string} 8 ; defining the result to be given back by the function. 9 9 ; (see examples) 10 10 ; … … 12 12 ; name of the function to be created. 13 13 ; 14 ; @keyword KWDLIST {in} 15 ; a vector string.to specify a list of keywords that must be included in the14 ; @keyword KWDLIST {in} {type=vector string} 15 ; to specify a list of keywords that must be included in the 16 16 ; function definition. 17 17 ; Warning: the string must start with a ',' -
trunk/SRC/Utilities/createpro.pro
r239 r242 5 5 ; 6 6 ; @param command {in}{required}{type=string array} 7 ; a string array defining the procedure to be created.7 ; array defining the procedure to be created. 8 8 ; each element will be a line of the created procedure. 9 9 ; … … 11 11 ; name of the procedure to be created. 12 12 ; 13 ; @keyword KWDLIST {in} 14 ; a vector string. 13 ; @keyword KWDLIST {in} {type=vector string} 15 14 ; to specify a list of keywords that must be included in the procedure 16 15 ; definition. … … 25 24 ; 26 25 ; @restrictions 27 ; - is not working with functions, use createfuncinstead.26 ; - is not working with functions, use <pro>createfunc</pro> instead. 28 27 ; - arguments can be given only through keywords. 29 28 ; - ends the procedure name with '.pro' if needed. … … 43 42 ; @version 44 43 ; $Id$ 44 ; 45 45 ;- 46 46 ; -
trunk/SRC/Utilities/find.pro
r239 r242 7 7 ; By default look for files included in !path 8 8 ; 9 ; all file_searchkeywords can be used.9 ; all <proidl>file_search</proidl> keywords can be used. 10 10 ; 11 11 ; @categories 12 12 ; find a file 13 13 ; 14 ; @param FILEIN {in}{required} 15 ; A scalar or array variable of string type, containing 16 ; file names to match. Input names specifications may contain 14 ; @param FILEIN {in}{required} {type=scalar string or array of strings} 15 ; File name[s] to match. Input names specifications may contain 17 16 ; wildcard characters, enabling them to match multiple files 18 ; (see file_searchfor more informations). By default and if19 ; necessary, findis looking for filename and also for filename17 ; (see <proidl>file_search</proidl> for more informations). By default and if 18 ; necessary, <pro>find</pro> is looking for filename and also for filename 20 19 ; completed with '.pro' 21 20 ; … … 23 22 ; activate this keyword to stop looking for the file as soon as we found one. 24 23 ; 25 ; @keyword IODIRECTORY {default=['.',!path]} 26 ; A scalar or array variable of string type, containing 27 ; directories names where we are looking for the file. 24 ; @keyword IODIRECTORY {type=scalar string or array of strings} {default=['.',!path]} 25 ; Directories names where we are looking for the file. 28 26 ; Different directories can be separated by 29 27 ; path_sep(/search_path) (':' on unix type machine) as it is done … … 47 45 ; @keyword RECURSIVE 48 46 ; performs recursive searching of directory hierarchies. 49 ; In a recursive search, findlooks recursively for any and all47 ; In a recursive search, <pro>find</pro> looks recursively for any and all 50 48 ; subdirectories in the file hierarchy rooted at the IODIRECTORY argument. 51 49 ; 52 50 ; @keyword REPERTOIRE 53 ; obsolete. keep for compatibility, use directorykeyword51 ; obsolete. keep for compatibility, use IODIRECTORY keyword 54 52 ; 55 53 ; @keyword UNIQUE … … 57 55 ; 58 56 ; @keyword TRYFIND 59 ; if the file was not found and this keyword is activated, find will call 57 ; if the file was not found and this keyword is activated, <pro>find</pro> 58 ; will call 60 59 ; itself with the keywords /LOOKALLDIR and /FIRSTFOUND to try to find 61 60 ; the file we are looking for. Note that if the file was found at the … … 68 67 ; A scalar or array variable of string type, containing the 69 68 ; name (with the full path of the matching files. If no files 70 ; exist with names matching the input arguments, findreturns69 ; exist with names matching the input arguments, <pro>find</pro> returns 71 70 ; the scalar string : 'NOT FOUND' 72 71 ; 73 72 ; @examples 74 ;75 73 ; IDL> print, find('*loadct') 76 74 ; /usr/local/rsi/idl_6.0/lib/utilities/xloadct.pro … … 106 104 ; @version 107 105 ; $Id$ 106 ; 108 107 ;- 109 108 ; … … 112 111 , ONLYNC = onlync, UNIQUE = unique, FIRSTFOUND = firstfound $ 113 112 , LOOKALLDIR = LOOKALLDIR, TRYFIND = tryfind, _EXTRA = ex 114 ; define where we look for the file115 113 ; 116 114 compile_opt idl2, strictarrsubs 117 115 ; 116 ; define where we look for the file 118 117 cd, current = current 119 118 current = (file_search(current, /test_directory, /mark_directory))[0] -
trunk/SRC/Utilities/isafile.pro
r237 r242 3 3 ; @file_comments 4 4 ; same as <pro>find</pro> except that as long as the file is 'NOT FOUND', 5 ; isafile calls dialog_pickfile, to ask the user to select a file. 5 ; <pro>isafile</pro> calls 6 ; <proidl>dialog_pickfile</proidl>, to ask the user to select a file. 6 7 ; 7 8 ; @categories … … 32 33 ; @keyword RECURSIVE 33 34 ; performs recursive searching of directory hierarchies. 34 ; In a recursive search, findlooks recursively for any and all35 ; In a recursive search, <pro>find</pro> looks recursively for any and all 35 36 ; subdirectories in the file hierarchy rooted at the IODIRECTORY argument. 36 37 ; … … 44 45 ; 45 46 ; @examples 46 ;47 47 ; IDL> print, isafile('/Users/sebastie/SAXO_RD/Commons/cm_4mesh.pro') 48 48 ; /Users/sebastie/SAXO_RD/Commons/cm_4mesh.pro -
trunk/SRC/Utilities/linearequation.pro
r231 r242 10 10 ; 11 11 ; @param POINT1 {in}{required} 12 ; This is the first point of (the) straight line(s) whose we want to calculate12 ; This is the first point of (the) straight line(s) whose we want to calculate 13 13 ; equation(s) 14 14 ; 15 15 ; @param POINT2 {in}{required} 16 ; This is the second point of (the) straight line(s) whose we want to calculate16 ; This is the second point of (the) straight line(s) whose we want to calculate 17 17 ; equation(s) 18 18 ; -
trunk/SRC/Utilities/lineintersection.pro
r231 r242 10 10 ; @param ABC1 {in}{required}{type=3d array} 11 11 ; is the first array of dimension 3, number_of_pairs_of_straight_lines, 12 ; whose each line contain the 3 parameters a, b and c of the first linear12 ; whose each line contain the 3 parameters a, b and c of the first linear 13 13 ; equation of the type ax+by+c=0 14 14 ; 15 15 ; @param ABC2 {in}{required}{type=3d array} 16 16 ; is second array of dimension 3, number_of_pairs_of_straight_lines, 17 ; whose each line contain the 3 parameters a, b and c of the second linear17 ; whose each line contain the 3 parameters a, b and c of the second linear 18 18 ; equation of the type ax+by+c=0 19 19 ; … … 26 26 ; 1) by default: it is a vector of complex whose each element is the coordinates 27 27 ; of the intersection point of a pair of straight lines. 28 ; 2) if FLOAT is activated, it is a array of re els of dimension 2,28 ; 2) if FLOAT is activated, it is a array of reals of dimension 2, 29 29 ; number_of_pairs_of_straight_lines whose each row is the coordinates 30 30 ; of the intersection point of a pair of straight line. 31 31 ; 32 32 ; @restrictions 33 ; If the 2 straight line are parallel, we return coordinates33 ; If the 2 straight lines are parallel, we return coordinates 34 34 ; (!values.f_nan,!values.f_nan) 35 35 ; -
trunk/SRC/Utilities/mergeonline_help.pro
r239 r242 15 15 ; @version 16 16 ; $Id$ 17 ; 17 18 ;- 18 19 ; … … 24 25 idlversion = float(strmid(!version.release, 0, 3)) 25 26 IF idlversion LT 6.2 THEN BEGIN 26 print, 'Warning: You need at least IDL 6.2 to use SAXO/IDL merged online help'27 ras = report('Warning: You need at least IDL 6.2 to use SAXO/IDL merged online help') 27 28 return 28 29 ENDIF … … 170 171 putfile, homesrc + 'aboutsaxo.txt', temporary(about) 171 172 ;--------------------------------------------------------------- 172 print, 'Merge of SAXO and IDL online help done...'173 ras = report('Merge of SAXO and IDL online help done...') 173 174 !help_path = homesrc 174 175 ; 175 176 RETURN 176 END177 END -
trunk/SRC/Utilities/protype.pro
r231 r242 33 33 ; @version 34 34 ; $Id$ 35 ; 35 36 ;- 36 37 ; 37 38 FUNCTION protype, file 38 ;39 39 ; 40 40 compile_opt idl2, strictarrsubs -
trunk/SRC/Utilities/report.pro
r239 r242 4 4 ; Like <proidl>dialog_message</proidl> if there is already some widget 5 5 ; active or like <proidl>message</proidl> if there is not any widget active. 6 ; To ask a question whose answer is not yes/no, use xquestion.6 ; To ask a question whose answer is not yes/no, use xquestion. 7 7 ; 8 ; @param TEXT {in}{required} 9 ; one string or one vector of string. Si le string ne8 ; @param TEXT {in}{required} {type=scalar string or arrays of string} 9 ; If TEXT is a scalar string, we look for the line feed characters "!C" 10 10 ; comporte qu''un element, on cherche les eventuels caracteres de 11 11 ; retour a la ligne: '!C'. If text is set to an array of strings, each … … 14 14 ; @keyword SIMPLE 15 15 ; activate to print only the message without the name 16 ; and the line of the routine (defined by calling routine_name) 17 ; 18 ; @keyword _EXTRA 19 ; Used to pass keywords to <proidl>dialog_message</proidl> and 20 ; <proidl>message</proidl> 16 ; and the line of the routine (defined by calling <pro>routine_name</pro>) 17 ; or++ 18 ; Activate to print the error message without printing the routine name with 19 ; its full path. 21 20 ; 22 21 ; @keyword PARENT … … 30 29 ; "Question" dialog. 31 30 ; 32 ; @keyword SIMPLE33 ; Activate to print the error message without printing the routine name with34 ; its full path.31 ; @keyword _EXTRA 32 ; Used to pass keywords to <proidl>dialog_message</proidl> and 33 ; <proidl>message</proidl> 35 34 ; 36 35 ; @returns -
trunk/SRC/Utilities/routine_name.pro
r231 r242 16 16 ; 17 17 ; @restrictions 18 ; This function use the keyword OUTPUT in help.pro and it is specified 18 ; This function use the keyword OUTPUT in <proidl>help</proidl> and 19 ; it is specified 19 20 ; in the on-line help that the return syntax of this word can change in 20 21 ; function of the version of the code. This version works with IDL 5.2. … … 43 44 FUNCTION routine_name, pilingnum 44 45 ; 45 ;46 46 compile_opt idl2, strictarrsubs 47 47 ; -
trunk/SRC/Utilities/testvar.pro
r231 r242 2 2 ; 3 3 ; @file_comments 4 ; A kind of keyword_set but when the value exist, it send it back. 4 ; A kind of <proidl>keyword_set</proidl> but when the value exist, it 5 ; send it back. 5 6 ; 6 7 ; @categories -
trunk/SRC/Utilities/text_box.pro
r231 r242 3 3 ; @file_comments 4 4 ; This procedure writes a short text message within a box-shaped 5 ; area in a graphic s window.The message may be split at word5 ; area in a graphic window. The message may be split at word 6 6 ; boundaries into several lines, and the character size and 7 7 ; orientation may be adjusted for the text to fit within the box. 8 8 ; 9 ; @param TEXT {in}{required} 10 ; ASCII text string containing the message.9 ; @param TEXT {in}{required} {type=string} 10 ; message in ASCII. 11 11 ; 12 12 ; @keyword POS 13 ; 4 element vector specifying the box position and size14 ; pos[0],pos[1] specify the lower left corner coordinate 15 ; pos[2],pos[3] specify the upper right corner coordinate 16 ; data window normalized coordinates are use 13 ; 4 elements vector specifying the box position and size 14 ; pos[0],pos[1] specify the lower left corner coordinate, 15 ; pos[2],pos[3] specify the upper right corner coordinate, 16 ; data window normalized coordinates are used. 17 17 ; 18 18 ; @keyword FG_COLOR {default=0} … … 39 39 ; 40 40 ; @keyword BOX 41 ; activate to show the box on graphic swindow.41 ; activate to show the box on graphic window. 42 42 ; 43 43 ; @history … … 53 53 PRO text_box,text,pos=pos,fg_color=fg_color,bg_color=bg_color,$ 54 54 center=center,right=right,box=box,vert_space=vert_space, _EXTRA = ex 55 ;56 55 ; 57 56 compile_opt idl2, strictarrsubs … … 182 181 return 183 182 end 184 -
trunk/SRC/Utilities/undefine.pro
r232 r242 3 3 ; @file_comments 4 4 ; erase a variable 5 ; same thing that delvarbut usable in a program and usable5 ; same thing like <proidl>delvar</proidl> but usable in a program and usable 6 6 ; for one variable simultaneously 7 7 ; … … 23 23 ; <a href="http://www.dfanning.com"/> : 24 24 ;QUESTION: How do I make an IDL variable have a type "undefined"? 25 ;ANSWER: At the main IDL level you can use the IDL procedure DELVARto25 ;ANSWER: At the main IDL level you can use the IDL procedure <proidl>DELVAR</proidl> to 26 26 ;delete an IDL variable and make it undefined. Inside of procedures 27 ;and functions, I use this little program named UNDEFINEthat I got27 ;and functions, I use this little program named <pro>UNDEFINE</pro> that I got 28 28 ;from Andrew Cool at the DSTO High Frequency Radar Division in 29 29 ;Adelaide, Australia. -
trunk/SRC/Utilities/xfile.pro
r239 r242 2 2 ; 3 3 ; @file_comments 4 ; display in a widget an ASCII file.4 ; display an ASCII file in a widget. 5 5 ; It is the same thing that <proidl>xdisplayfile<proidl> but here, we use it 6 6 ; to display the content of a procedure or of a function located in the !path -
trunk/SRC/Utilities/xhelp.pro
r239 r242 7 7 ; Widget 8 8 ; 9 ; @param FILENAME {in}{required} 10 ; A scalar string that contains the filename of the file to display.11 ; F ilenameshould be located in !path.9 ; @param FILENAME {in}{required} {type=scalar string} 10 ; the name of the file to display. 11 ; FILENAME should be located in !path. 12 12 ; ".pro" suffix will be appended if needed. 13 13 ; … … 16 16 ; 17 17 ; @restrictions 18 ; Triggers the XMANAGERif it is not already in use.18 ; Triggers the <proidl>XMANAGER</proidl> if it is not already in use. 19 19 ; 20 20 ; @examples
Note: See TracChangeset
for help on using the changeset viewer.