. . . then just substitute this code for the existing contents of /usr/bin/mtpaintsnapshot.sh:
Code: Select all
#!/usr/bin/env tclsh
package require Gnocl
set now [gnocl::button -text "Capture Now!" -onClicked {
$win delete
update
exec mtpaint -s
}]
set can [gnocl::button -text "Cancel" -onClicked {$win delete}]
set nowbox [gnocl::box -orientation horizontal \
-children [list $now $can] -fill {1 1} -expand 1]
set wait [gnocl::button -text "Wait: " -onClicked snap]
set secs 10
set num [gnocl::spinButton -digits 0 -variable secs]
set blab [gnocl::label -text " seconds"]
set waitbox [gnocl::box -orientation horizontal \
-children [list $wait $num $blab] -fill {1 1} -expand 1]
set bigbox [gnocl::box -orientation vertical \
-children [list $nowbox $waitbox]]
set win [gnocl::window -child $bigbox -title "mtPaint Capture"]
proc snap {} {
$::wait configure -text "Waiting"
after [expr {$::secs * 1000}] {
$::win delete
update
exec mtpaint -s
}
}
There was a rogue driver set that I added early in the Alpha series which was masking the internal driver support. I have removed that for the next release and I expect wireless will work at least as well as it did in 4.12 .. we'll see, eh? 
Puppy will neither live nor die simply because you decided one way or the other. The next release will have the workaround embedded so the wireless problems should be fixed by then. We'll see. 
I thought the idea behind (temporarily) getting rid of Tcl/Tk was to standardize the GTK+ 2 look, which (on the whole) is better than what you're likely to get with Tk, and far better than what you can get with xdialog and the like. It turns out, I believe, that reinstituting Tcl with Gnocl actually helps to standardize the GTK+ look, as in this little script. So, um, if you (or anyone else) would like to discuss any remaining reasons for possibly dumping Tcl, maybe a new thread on that point could be started.
