ltk-user

ltk-user@common-lisp.net

259 discussions

Re: [ltk-user] Very noob question
by Thomas F. Burdick 20 Jan '06

20 Jan '06

By the way, when reporting bugs/issues it's helpful to say what lisp implementation you're using, and what OS/architecture. On 1/20/06, Arie van Wingerden <xapwing(a)gmail.com> wrote: > Hi Thomas, > > thanks for your answer. > However, I now get another error. > I execute the steps as you suggested, which works well. > After that I execute: > (ltktest) > as in the example and I get this trace info: > > Win32 error 2 (ERROR_FILE_NOT_FOUND): The system cannot find the file > specified. > [Condition of type SYSTEM::SIMPLE-OS-ERROR] Since you're running on Windows, have you installed Tcl/Tk? If not, you can download it from here: http://www.activestate.com/Products/Download/Download.plex?id=ActiveTcl You will need to make sure that the *wish-pathname* variable is set to the path to wish.exe (eg, "C:\Tcl\bin\wish.exe"). This is omitted from the simplest example because typical Unix systems have tcl/tk installed and wish in the path. The installation instructions should probably be updated to mention Windows issues. > Hope this makes the problem evident for you! > Thanks for your help! No problem -- let me know if this works for you. (And be sure to hit "Reply to all" so you'll get the list as well).

2 2

[ltk-user] Very noob question
by Arie van Wingerden 20 Jan '06

20 Jan '06

Hi, when trying to install LTK I get an error with (use-package 'ltk) The (compile-file "ltk") works fine. The (load "ltk") works also fine. But (use-package 'ltk) produces the following error: (USE-PACKAGE (#<PACKAGE LTK>) #1=#<PACKAGE COMMON-LISP-USER>): 1 name conflicts remain Which symbol with name "VALUE" should be accessible in #1#? [Condition of type SYSTEM::SIMPLE-PACKAGE-ERROR] I don't understand it, because I haven't worked with packages yet. Any ideas? -- Met vriendelijke groet / with kind regards, Arie van Wingerden

2 1

Fwd: [ltk-user] paren-matching entry widgets, and unbinding the TAB key.
by Peter Herth 10 Jan '06

10 Jan '06

I forget to reply to all, so here is my reply ---------- Forwarded message ---------- From: Peter Herth <herth(a)peter-herth.de> Date: Jan 9, 2006 11:25 PM Subject: Re: [ltk-user] paren-matching entry widgets, and unbinding the TAB key. To: michael graffam <mikegraffam(a)yahoo.com> On 1/9/06, michael graffam <mikegraffam(a)yahoo.com> wrote: > Hello all, > > I was wondering if someone on this list might be able > to help me make a parenthesis matching entry widget? > > What I need to know is how (if it is even possible) I > can find where the text cursor is in an entry widget. > The approach I'd like to use is to bind #\) to a > function which looks at the current position of the > text cursor and iterates backwards through the string > looking for the matching #\( .. then the icursor > position will be set to this location for a second to > indicate to the user the matching paren, and then > placed back to the original position. This is really tricky, I just browsed through the Tk docs to the entry widget, and my conclusion is, that it probably is a better idea to use a one-line text widget, this gives you many more options for inquiring the widgets state as well as for the display (like flashing the matching parens in color) > The second question that I have is how I might unbind > the TAB key in my entry widget so that hitting TAB > will not move focus to the next widget in the window. > I'd like TAB to invoke my auto-completion routine > (using Control-Space at the moment). You need to prevent the propagation of the TAB keypress to the widget. One can do this by binding an event so it does not propagate. Do do this I added the :exclusive keyword argument to bind, this will be in the next released version of Ltk. Peter -- Dipl.-Phys. Peter Herth

1 0

[ltk-user] paren-matching entry widgets, and unbinding the TAB key.
by michael graffam 09 Jan '06

09 Jan '06

Hello all, I was wondering if someone on this list might be able to help me make a parenthesis matching entry widget? What I need to know is how (if it is even possible) I can find where the text cursor is in an entry widget. The approach I'd like to use is to bind #\) to a function which looks at the current position of the text cursor and iterates backwards through the string looking for the matching #\( .. then the icursor position will be set to this location for a second to indicate to the user the matching paren, and then placed back to the original position. The second question that I have is how I might unbind the TAB key in my entry widget so that hitting TAB will not move focus to the next widget in the window. I'd like TAB to invoke my auto-completion routine (using Control-Space at the moment). Thanks for you help. Mike __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com

1 0

[ltk-user] Ltk v 0.88 sneak preview
by Peter Herth 15 Dec '05

15 Dec '05

Hi, to all on this mailinglist, especially all the new members who joined today :). The next release of Ltk is more than overdue and I just uploaded the newest version to my server. So please get it and try to find any showstoppers, then I can formally release it soon. You can find it here: http://www.peter-herth.de/ltk/ltk-0.88pre1.lisp and do not heasitate to give feedback/questions/etc. Peter

1 0

[ltk-user] bug?
by Yaroslav Kavenchuk 05 Dec '05

05 Dec '05

Hi! clisp-2.36, ltk-0.876, Active Tcl 8.4.11.2, win2k All tests - (ltktest) and (ltk::ltk-eyes) - run without errors. But example from ltkdoc: [3]> (defun hello-1() (with-ltk () (let ((b (make-instance button :master nil :text "Press Me" :command (lambda () (format t "Hello World!~&"))))) (pack b)))) HELLO-1 [4]> (hello-1) proc escape {s} {regsub -all {\\} $s {\\\\} s1;regsub -all {"} $s1 {\"} s2;return $s2} proc senddata {s} {puts "(:data [escape $s])";flush stdout} proc senddatastring {s} {puts "(:data \"[escape $s]\")";flush stdout} proc senddatastrings {strings} { puts "(:data (" foreach s $strings { puts "\"[escape $s]\"" } puts "))";flush stdout} proc sendevent {s x y keycode char width height root_x root_y mouse_button} {puts "(:event \"$s\" $x $y $keyco de $char $width $height $root_x $root_y $mouse_button)"} proc callback {s} {puts "(:callback \"$s\")";flush stdout} proc callbackval {s val} {puts "(:callback \"$s\" $val)"} proc callbackstring {s val} {puts "(:callback \"$s\" \"[escape $val]\")"} *** - EVAL: variable BUTTON has no value The following restarts are available: USE-VALUE :R1 You may input a value to be used instead of BUTTON. STORE-VALUE :R2 You may input a new value for BUTTON. ABORT :R3 ABORT Break 1 [5]> Thansk! -- WBR, Yaroslav Kavenchuk.

2 2

[ltk-user] Ltk 0.878 release
by Peter Herth 05 Jul '05

05 Jul '05

Hi, I just uploaded the newest Ltk version to my server: http://www.peter-herth.de/ltk/ (note that you have to download ltk-0.878.lisp, as I don't want to put it in the "official" tarball without further testing :) Besides many small fixes, there are two mayor changes. First, with-ltk takes keyword parameters now , which configure the condition/error handling it does now (so you can if an error occors choose to restart mainloop for example) Secondly, the whole widget class generation code has been completely rewritten, using a macro to replace the rather long definitions, cutting 20k of the Ltk code ... So, if anyone out there feels like giving it a test ride and give some feedback, I might release it officially soon. Peter

1 0

[ltk-user] LTK isn't extensible
by Chris Capel 14 Dec '04

14 Dec '04

I've run up against LTK's incompleteness a couple times now. First, I wanted to be able to change the default color of shapes drawn on a canvas. My quick fix was to create an optional parameter to create-oval that passes its argument on at the end of the command to wish. Not exactly an ideal fix. The second time was when I wanted to change the back color of my canvas to black, which I will probably work around by changing the default color of the canvas created by the canvas class to black. Again, not a clean fix. Now, it would be possible to complete LTK by adding all the possible parameters to every command as arguments or slots, depending on how that command is abstracted. I assume that, with enough interest, this is the eventual goal. It would also be possible to have everything accept optional parameters to let users stick parameters onto the ends of things (but they still have to know the parameters exist, and to know tcl syntax, and probably sometimes to look at the source to figure out which command is being issued for a given ltk function). For the time being, the latter option seems to be the best choice. Would Peter like me to look into adding this to LTK? Perhaps he'd rather take on the project? Chris Capel -- "What is it like to be a bat? What is it like to bat a bee? What is it like to be a bee being batted? What is it like to be a batted bee?" -- The Mind's I (Hofstadter, Dennet)

2 1

[ltk-user] First post
by Peter Herth 25 Nov '04

25 Nov '04

Welcome to all subscribers of ltk-user. Here is the place to discuss anything Ltk-related. Peter

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

ltk-user