Skip to main content

Checking to see which entry has the active input focus.

Gtk provides no simple way telling a calling program which entry widget contains the active keyboard focus. Specific widgets can be interrogated as to whether they possess keyboard input focus on either a global scale or simply within their own toplevel window. My own pet project is working on the translation of Chinese texts and the api of my translation editor will have multiple editable widgets on screen at any one time. Up till now I've used focus events to set a global variable identifying which widget has focus, but there are other ways. Today I just added the hasToplevelFocus and has hasGlobalFocus commands to the gnocl::text widget. There always was, of course the option to use cget -hasFocus. Here's my test script.

#---------------
# test-chinese-punct-toolbar.tcl
#---------------
#
#!/bin/sh
#\
exec tclsh "$0" "$@"

package require Gnocl

#---------------
# insert punc mark it currently active text
#---------------
proc do_chn_punc { mark } {

    foreach w $::texts {
        if { [$w isToplevelFocus] == 1 } {
            $w insert cursor $mark
        }
    }
}

#---------------
# Insert punctuation marks suited to differing character sets.
#---------------
proc chn_punc { {type jianti} } {

    set marks {
        。    {Full Stop}
        ‘    {Open Single Quote}
        “    {Open Double Quote}
        ”    {Close Double Quote}
        ’    {Close Single Quote}
        、    {Enumeration comma}
        ‧    {Middle dot}
        《    {Open Double Title Mark}
        》    {Close Double Title Mark}
        ……    {Ellipsis}
        ——    {Em Dash}
        —    {En Dash}
        ~    {Wavy Dash}
        }

    if {$type eq "fanti" } {   
    set marks {
        。    {Full Stop}
        「    {Open Single Quote}
        『    {Open Double Quote}
        』    {Close Double Quote}
        」    {Close Single Quote}
        、    {Enumeration comma}
        ‧    {Middle dot}
        《    {Open Double Title Mark}
        〈    {Open Single (Section) Title Mark}
        〉    {Close Single (Section) Title Mark}
        》    {Close Double Title Mark}
        ……    {Ellipsis} 
        ——    {Em Dash}
        —    {En Dash}
        ~    {Wavy Dash}
    } }

    set tb [gnocl::toolBar -style text ]
       
    foreach {mark tip} $marks {
        $tb add item \
            -icon %#New \
            -text $mark \
            -tooltip $tip \
            -onClicked "do_chn_punc $mark"
    }
   
    return $tb
}


set box [gnocl::box -orientation vertical]
set txt(1) [gnocl::text -baseFont {Serif 12}]
set txt(2) [gnocl::text -baseColor #D1FEFF -baseFont {Serif 14}]
gnocl::window -child $box
$box add [chn_punc]
$box add [chn_punc fanti]
$box add $txt(1)
$box add $txt(2)

# list of available texts
set texts [list $txt(1) $txt(2)]
puts $texts

$txt(1) grabFocus





Comments

Popular posts from this blog

gnocl::calendar

Given this module some attention today. Added some of the more package wide options to the module and created customised handler for setting the month. (For some odd reason months are are counted 0-11 whereas days are 1-31.) There's still a little more to do to this one including the addition of code to store diary details. Here's the working test script to show the range of options at work. The percentage substitution string item %e explores something that I've been toying with, the name of the signal/event that initiated the call. Ok, a script can keep its own internal trace but who knows, it might prove useful. #--------------- # calendarTest.tcl #--------------- # Author:   William J Giddings # Date:     07/05/09 #--------------- #!/bin/sh # the next line restarts using tclsh \ exec tclsh "$0" "$@" #--------------- package require Gnocl set cal [gnocl::calendar] $cal configure -day 8 -month 7 -year 1956 $cal configure -rowHeight 1 -colWidth 1 $ca...

Creating icons from UTF-8 Characters.

Linux distros have heaps of pre-installed icons ready for use. I recently needed to create a toolbar menu which needed to access a set of unique icons which contained single characters. It was, in fact, a pull down menu for the insertion of 'special characters'. The Gtk+ api has complete functionality for creating icons from pixbufs and Gnocl providing convenient access.  Here's a screenshot and the script.     # !/bin/sh # the next line restarts using tclsh \ exec tclsh "$0" "$@" package require Gnocl if { [namespace exists jmls] == 0} {     namespace eval jmls {} } set ::app(specialCharacters)  [list Section ¶ Paragraph § Separator • Left-Arrow ← Up-Arrow ↑ Right-Arrow → Down-Arrow ↓ Root √] proc jmls::charIcon {name ch} {          set pb1 [gnocl::pixBuf new -width 40 -height 40]     $pb1 text \         -position [list 15 30] \         -font [list...

Getting Widget Style Properties

Until the move over to Gtk4, Gnocl is still built against the Gtk 2.21 libraries. One of the inconveniences of Gtk is getting and setting widget style settings which are considered to be set globally by the desktop style settings and not for the programmer to tinker around with. Needless to say, there are times when different defaults are preferred, largely to draw the users attention to 'something a bit different'. The function gtk_widget_modify_font  is a convenience function to set the widget basefont as shown in this snippet from the button.c module,  if ( options[baseFontIdx].status == GNOCL_STATUS_CHANGED ) { GtkWidget *label; label = gnoclFindChild ( GTK_WIDGET ( para->button ), GTK_TYPE_LABEL ); PangoFontDescription *font_desc = pango_font_description_from_string ( Tcl_GetString ( options[baseFontIdx].val.obj ) ); gtk_widget_modify_font ( GTK_WIDGET ( label ), font_desc ); pango_font_description_free ( font_desc ); } Unfortunately, there's no d...