> puretkgui
Running openSUSE 11.0 with Tcl 8.5.2 and tk 8.5.2
ran the command tclsh.main.tcl
got the following messages:
package "tooltip" is not available
Xml package is missing
Application opened but I don't see any widgets
Hello Paul.
The 'missing tooltip package' is only a warning, and PureTkGUI works
correctly even in this case.
The fact you don't see any widget is normal. I suppose you envision
toolbars with widgets that you could drag and drop into the workspace.
Actually, you have to add it thanks to a right click on the workspace
or by using the Widgets menu.
This concept is quite different from other GUI builders, but it's
certainly more efficient once you get used to it.
Keep me informed if you cannot figure out how it works.
Regards,
Thomas
Thanx, I kinda see how it works now. It is going to take this
chronologically advantaged person awhile to get the hang of it and a lot of
playing around. Is there a manual that you will have available soon?
I have just dabbled in tcl/tk and am not a programmer. I have though, in
the past developed one small program to help me in my winemaking
calculations but it was a PITA to configure the location of all the
widgets.
strace:
...
read(5, 0x2294d14, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
open("/usr/share/fonts/X11/Type1/n019004l.pfb", O_RDONLY) = 7
fcntl(7, F_SETFD, FD_CLOEXEC) = 0
fstat(7, {st_mode=S_IFREG|0644, st_size=70730, ...}) = 0
mmap(NULL, 70730, PROT_READ, MAP_PRIVATE, 7, 0) = 0x7f39ad2cd000
close(7) = 0
brk(0x35c5000) = 0x35c5000
select(6, [5], [5], NULL, NULL) = 1 (out [5])
writev(5,
[{"7\24\7\0\367\7\0\2\246\1\0\0T\0\0\0\377\200\200\0\1\0\0\0\3\0\0\0<\24\2\0\366"...,
1052}], 1) = 1052
select(6, [5], [], NULL, NULL) = 1 (in [5])
read(5,
"\0015\234)\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\304h\0\0\0\0\0\0"...,
4096) = 32
read(5, 0x2294d14, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
...
writev(5,
[{"7\30\7\0\21\10\0\2\246\1\0\0\10@\1\0\357\357\357\0\20\10\0\2\0\0\0\0007\30\7\0\22"...,
752}], 1) = 752
select(6, [5], [], NULL, NULL) = 1 (in [5])
read(5,
"\21\7\330)\24\10\0\2\24\10\0\2\0\0\0\0\20\0\0\0\0\0\0\0PH\354\2\0\0\0\0\1"...,
4096) = 64
read(5, 0x2294d14, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
$ wish
% info patchlevel
8.5.7
Where to begin search for the bug?
--
Gerhard Reithofer
Tech-EDV Support Forum - http://support.tech-edv.co.at
Hello Paul,
Don't be afraid, PureTkGUI is easy and more generally Tcl/Tk is one of
the easiest scripting languages out there. The learning curve for
those is not that steep actually, and you could indeed get productive
over time very quickly.
Regarding help, manuals and tutorials, yes, something is planned, but
I'm still working very hard on the next PureTkGUI versions that will
bring even more convenience for widgets management. My plans are to
get that v1.0.0 out and then move on to making a collection of video
tutorials covering the basics of PureTKGUI. They will be a great help
for those not familiar with Tcl/Tk.
Don't hesitate to post suggestions for improvement whenever you see
them fit.
Thomas
Hi Gerhard,
Nice stack trace you've got there ;-)
First and foremost, PureTkGUI has been used by many many users and
still such serious issues haven't been reported yet. This does not
prove PureTkGUI is bug-free, but it certainly highlights the fact
you've used an unusual path when using PureTkGUI to encounter that seg
fault. We have to analyze this use case closely now.
Second, I would like to mention that PureTkGUI does not include *any*
compiled code (PureTkGUI is a set of Tcl/Tk scripts). Therefore the
segmentation fault you have happens either in Tcl/Tk itself or in one
of the used libraries. One of them could be faulty. To give you an
insight as to which of these could be the culprit, here are the
packages used by PureTkGUI :
- Tk 8.5 -- mandatory
- tooltip (from tcllib) -- optional
- xml -- optional
- BWidgets -- optional
- Tix -- optional
- Iwidgets (disabled by default !) -- optional
If you've enabled Iwidgets by renaming IWidgets.txt.disabled into
IWidgets.txt inside ./Widgets sub-directory, and you are running under
Ubuntu, then you are very likely to encounter what I've found : a seg
fault due to a broken incr package inside this distribution. You can
enable those Iwidgets under Windows with an ActiveState distribution
though, and they work fine. I have not spent any time working on this
seg fault as it lies outside the scope of PureTkGUI, and those
Iwidgets can't compare with the latest ttk ones anyway ;-).
If it still does not help you trouble shooting your problems, we could
go deeper and check the logs. PureTkGUI normally spits lots of things
to stdout (we are in a development phase). We could try to find where
it seg faults by looking at those logs. Could you please show them to
me ?
Thanks.
Thomas.
On Sat, 26 Dec 2009, Thomas MENEZ wrote:
> On 24 déc, 17:31, Gerhard Reithofer <gerhard.reitho...@tech-edv.co.at>
> wrote:
> > Hi *,
> > I get a segfault when trying puretkgui!
> >
> > strace:
> > ...
> > read(5, 0x2294d14, 4096) = -1 EAGAIN (Resource
...
> > "\21\7\330)\24\10\0\2\24\10\0\2\0\0\0\0\20\0\0\0\0\0\0\0PH\354\2\0\0\0\0\1"...,
> > 4096) = 64
> > read(5, 0x2294d14, 4096) = -1 EAGAIN (Resource
> > temporarily unavailable)
> > --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> > +++ killed by SIGSEGV +++
> >
> > $ wish
> > % info patchlevel
> > 8.5.7
...
> Hi Gerhard,
> Nice stack trace you've got there ;-)
>
> First and foremost, PureTkGUI has been used by many many users and
> still such serious issues haven't been reported yet. This does not
> prove PureTkGUI is bug-free, but it certainly highlights the fact
> you've used an unusual path when using PureTkGUI to encounter that seg
> fault. We have to analyze this use case closely now.
>
> Second, I would like to mention that PureTkGUI does not include *any*
> compiled code (PureTkGUI is a set of Tcl/Tk scripts). Therefore the
> segmentation fault you have happens either in Tcl/Tk itself or in one
> of the used libraries. One of them could be faulty. To give you an
> insight as to which of these could be the culprit, here are the
> packages used by PureTkGUI :
Yes, I'm aware of that.
I addressed * (i.e. all TCL users) and I think that the bug may be in
the Tix part, which is a binary extension.
I also have to add the information, that it is the 64-bit version
(forgot the tcl_platform listing) and the tool is running on other
machines (with different Active-Tcl contents) without crash.
The instalation is a full Activestate dist and I thought they could give
me some hints to analyze the situation.
> - Tk 8.5 -- mandatory
> - tooltip (from tcllib) -- optional
> - xml -- optional
> - BWidgets -- optional
> - Tix -- optional
... suspected extension
> - Iwidgets (disabled by default !) -- optional
>
> If you've enabled Iwidgets by renaming IWidgets.txt.disabled into
> IWidgets.txt inside ./Widgets sub-directory, and you are running under
> Ubuntu, then you are very likely to encounter what I've found : a seg
> fault due to a broken incr package inside this distribution. You can
> enable those Iwidgets under Windows with an ActiveState distribution
> though, and they work fine. I have not spent any time working on this
> seg fault as it lies outside the scope of PureTkGUI, and those
> Iwidgets can't compare with the latest ttk ones anyway ;-).
>
> If it still does not help you trouble shooting your problems, we could
> go deeper and check the logs. PureTkGUI normally spits lots of things
> to stdout (we are in a development phase). We could try to find where
> it seg faults by looking at those logs. Could you please show them to
> me ?
> Thanks.
> Thomas.
THX
You should contact Activestate by email. Or talk to tclguy on tkchat
(he's working for this company).
rgds
...
> You should contact Activestate by email. Or talk to tclguy on tkchat
> (he's working for this company).
I was never able to get tkchat running.
As it seems to be limited to a specific (older) version and platform, I
don't want to harras too many people and invest too much time in that
case (at least now).
Sorry, but I do not have any irc-client on my workstations where I work
mostly, which still are often Unixes.
I've never used any chat client and only once tried it on a Linux.
--
Witek
http://trimen.pl/witek/
I think you've already figured this out, but "because nobody's added it
yet" is the usual reason for why something isn't on the wiki. (FWIW, I
tend to only add pages when they're about something that's a special
interest to me, and I have an unapologetically old-school approach to
GUI writing.) Thankfully, you've corrected things. :-)
Donal.