File: Xrm.pod

package info (click to toggle)
perl-tk 1%3A804.036%2Bdfsg1-5
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 35,284 kB
  • sloc: ansic: 349,560; perl: 52,292; sh: 12,678; makefile: 5,700; asm: 3,565; ada: 1,681; pascal: 1,082; cpp: 1,006; yacc: 883; cs: 879
file content (45 lines) | stat: -rw-r--r-- 1,087 bytes parent folder | download | duplicates (14)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

=head1 NAME

Tk::Xrm - X Resource/Defaults/Options routines that obey the rules.

=for pm Tk/Xrm.pm

=for category Creating and Configuring Widgets

=head1 SYNOPSIS

   use Tk;
   use Tk::Xrm;

=head1 DESCRIPTION

Using this modules causes Tk's Option code to be replaced by versions
which use routines from <X11/Xresource.h> - i.e. same ones every other
X toolkit uses.

Result is that "matching" of name/Class with the options database follows
the same rules as other X toolkits. This makes it more predictable,
and makes it easier to have a single ~/.Xdefaults file which gives sensible
results for both Tk and (say) Motif applications.

=head1 BUGS

Currently B<optionAdd>(I<key> =E<gt> I<value>?, I<priority>?) ignores optional
priority completely and just does XrmPutStringResource().
Perhaps it should be more subtle and do XrmMergeDatabases() or
XrmCombineDatabase().

This version is a little slower than Tk's re-invention but there is
more optimization that can be done.

=head1 SEE ALSO

L<Tk::option|Tk::option>

=head1 KEYWORDS

database, option, priority, retrieve

=cut