.\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
.\" ========================================================================
.de Sh \" Subsection heading
.de Sp \" Vertical space (when we can't use .PP)
.de Vb \" Begin verbatim text
.de Ve \" End verbatim text
.\" Set up some character translations and predefined strings. \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote. | will give a
.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
. tm Index:\\$1\t\\n%\t"\\$2"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
. \" simple accents for nroff and troff
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
. \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
. \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
. \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
.\" ========================================================================
.IX Title "GETOPENFILE 1"
.TH GETOPENFILE 1 "2000-12-30" "perl v5.8.0" "User Contributed Perl Documentation"
getOpenFile, getSaveFile \- pop up a dialog box for the user to select a file to open or save.
\&\ \fI$widget\fR\->\fBgetOpenFile\fR(?\fI\-option\fR=>value, ...>?)
\&\ \fI$widget\fR\->\fBgetSaveFile\fR(?\fI\-option\fR=>value, ...>?)
The methods \fBgetOpenFile\fR and \fBgetSaveFile\fR pop up a
dialog box for the user to select a file to open or save.
The \fBgetOpenFile\fR method is usually associated with the \fBOpen\fR
command in the \fBFile\fR menu. Its purpose is for the user to select an
existing file \fIonly\fR. If the user enters an non-existent file, the
dialog box gives the user an error prompt and requires the user to give
an alternative selection. If an application allows the user to create
new files, it should do so by providing a separate \fBNew\fR menu command.
The \fBgetSaveFile\fR method is usually associated with the \fBSave\fR
as command in the \fBFile\fR menu. If the user enters a file that
already exists, the dialog box prompts the user for confirmation
whether the existing file should be overwritten or not.
If the user selects a file, both \fBgetOpenFile\fR and
\&\fBgetSaveFile\fR return the full pathname of this file. If the
user cancels the operation, both commands return an undefined value.
The following \fIoption-value\fR pairs are possible as command line
arguments to these two commands:
.IP "\fB\-defaultextension\fR => \fIextension\fR" 4
.IX Item "-defaultextension => extension"
Specifies a string that will be appended to the filename if the user
enters a filename without an extension. The default value is the empty
string, which means no extension will be appended to the filename in
any case. This option is ignored on the Macintosh platform, which
does not require extensions to filenames.
.IP "\fB\-filetypes\fR => [\fIfilePattern\fR ?, ...?]" 4
.IX Item "-filetypes => [filePattern ?, ...?]"
If a \fBFile types\fR listbox exists in the file dialog on the particular
platform, this option gives the \fIfiletype\fRs in this listbox. When
the user choose a filetype in the listbox, only the files of that type
are listed. If this option is unspecified, or if it is set to the
empty list, or if the \fBFile types\fR listbox is not supported by the
particular platform then all files are listed regardless of their
types. See \*(L"\s-1SPECIFYING\s0 \s-1FILE\s0 \s-1PATTERNS\s0\*(R" below for a
discussion on the contents of \fIfilePattern\fRs.
.IP "\fB\-initialdir\fR => \fIdirectory\fR" 4
.IX Item "-initialdir => directory"
Specifies that the files in \fIdirectory\fR should be displayed
when the dialog pops up. If this parameter is not specified, then
the files in the current working directory are displayed. This
option may not always work on the Macintosh. This is not a bug.
Rather, the \fIGeneral Controls\fR control panel on the Mac allows the
end user to override the application default directory.
.IP "\fB\-initialfile\fR => \fIfilename\fR" 4
.IX Item "-initialfile => filename"
Specifies a filename to be displayed in the dialog when it pops
up. This option is ignored by the \fBgetOpenFile\fR method.
.IP "\fB\-title\fR => \fItitleString\fR" 4
.IX Item "-title => titleString"
Specifies a string to display as the title of the dialog box. If this
option is not specified, then a default title is displayed. This
option is ignored on the Macintosh platform.
.SH "SPECIFYING FILE PATTERNS"
.IX Header "SPECIFYING FILE PATTERNS"
The \fIfilePattern\fRs given by the \fB\-filetypes\fR option
are a list of file patterns. Each file pattern is a list of the
\& typeName [extension ?extension ...?] ?[macType ?macType ...?]?
\&\fItypeName\fR is the name of the file type described by this
file pattern and is the text string that appears in the \fBFile types\fR
listbox. \fIextension\fR is a file extension for this file pattern.
\&\fImacType\fR is a four-character Macintosh file type. The list of
\&\fImacType\fRs is optional and may be omitted for applications that do
not need to execute on the Macintosh platform.
Several file patterns may have the same \fItypeName,\fR in which case
they refer to the same file type and share the same entry in the
listbox. When the user selects an entry in the listbox, all the files
that match at least one of the file patterns corresponding
to that entry are listed. Usually, each file pattern corresponds to a
distinct type of file. The use of more than one file patterns for one
type of file is necessary on the Macintosh platform only.
On the Macintosh platform, a file matches a file pattern if its
name matches at least one of the \fIextension\fR(s) \s-1AND\s0 it
belongs to at least one of the \fImacType\fR(s) of the
file pattern. For example, the \fBC Source Files\fR file pattern in the
sample code matches with files that have a \fB\e.c\fR extension \s-1AND\s0
belong to the \fImacType\fR \fB\s-1TEXT\s0\fR. To use the \s-1OR\s0 rule instead,
you can use two file patterns, one with the \fIextensions\fR only and
the other with the \fImacType\fR only. The \fB\s-1GIF\s0 Files\fR file type
in the sample code matches files that \s-1EITHER\s0 have a \fB\e.gif\fR
extension \s-1OR\s0 belong to the \fImacType\fR \fB\s-1GIFF\s0\fR.
On the Unix and Windows platforms, a file matches a file pattern
if its name matches at at least one of the \fIextension\fR(s) of
the file pattern. The \fImacType\fRs are ignored.
.SH "SPECIFYING EXTENSIONS"
.IX Header "SPECIFYING EXTENSIONS"
On the Unix and Macintosh platforms, extensions are matched using
glob-style pattern matching. On the Windows platforms, extensions are
matched by the underlying operating system. The types of possible
extensions are: (1) the special extension * matches any
file; (2) the special extension "" matches any files that
do not have an extension (i.e., the filename contains no full stop
character); (3) any character string that does not contain any wild
card characters (* and ?).
Due to the different pattern matching rules on the various platforms,
to ensure portability, wild card characters are not allowed in the
extensions, except as in the special extension *. Extensions
without a full stop character (e.g, ~) are allowed but may not
\& ['Text Files', ['.txt', '.text']],
\& ['TCL Scripts', '.tcl' ],
\& ['C Source Files', '.c', 'TEXT'],
\& ['GIF Files', '.gif', ],
\& ['GIF Files', '', 'GIFF'],
\& my $filename = $widget->getOpenFile(-filetypes=>$types);
\& if ($filename ne "") {
projects / OpenSPARC-T2-DV / blob