Thread: Midnight Commander: How to start mcedit from shell?
View Single Post
Old 09-01-2016, 12:41 PM   #19
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by nasser View Post
knc1, this is just a modification of baf's original kterm KUAL script.

If the screen width is NOT gt 600, then it uses the default "keyboard.xml" file, along with associated images in the img/ folder.

If the screen width IS gt 600(original logic to detect the then new PW1), then the "keyboard-wide.xml" file, along with the associated images(bigger) in the img-wide/ folder is used. These files are also used for the latest 300 ppi kindles, but we actually need a new "keyboard-extrawide.xml" file!
It got silently fixed.

The if grew an else statement while we where discussing it.

Or PARMS could have been initialized to the < 600 case and then modified if required.
Six of one, half a dozen of the other - author's choice.
knc1 is offline   Reply With Quote