text .. index anchor
in [TCL]
|
Prev: Why to use packages
Next: acomplia canadian pharmacies
From: Gerhard Reithofer on 2 Jan 2010 17:11 Hi, I mentionend that (my favourite tcl-only) editor ASED runs into errors when using it with 8.5. The reason for that is, that it uses the ".. index anchor" command which seems not to be supported from 8.5 on. I haven't found a information, that this (relaivtely serious?) change has bee made in text widget. Can anyone tell me a source where this (the change) has been documented? -- Gerhard Reithofer Tech-EDV Support Forum - http://support.tech-edv.co.at
From: Gerhard Reithofer on 2 Jan 2010 17:35 Hi, once more. On Sat, 2 Jan 2010, Gerhard Reithofer wrote: > Hi, > I mentionend that (my favourite tcl-only) editor ASED runs into errors > when using it with 8.5. > > The reason for that is, that it uses the ".. index anchor" command which > seems not to be supported from 8.5 on. > > I haven't found a information, that this (relaivtely serious?) change > has bee made in text widget. > > Can anyone tell me a source where this (the change) has been documented? I've investigated the problem more deep and it seems that it is not directly text related, maybe a ctext problem. I get the error message: ========================================= bad text index "anchor" while executing ".mainframe.frame.pw.pw.nb2.f/home/gerhardr/dot#Xmodmap.sw.textWindow._t index anchor" ("uplevel" body line 1) invoked from within "uplevel 2 $self._t $cmd $args" (procedure "ctext::instanceCmd" line 332) invoked from within "ctext::instanceCmd ..mainframe.frame.pw.pw.nb2.f/home/gerhardr/dot#Xmodmap.sw.textWindow index anchor" ("eval" body line 1) .... ========================================= But it is reproduceable, that I do not get the error message, if I run ased with Tcl 8.4 instead of 8.5! Any hints? TIA -- Gerhard Reithofer Tech-EDV Support Forum - http://support.tech-edv.co.at
From: Donal K. Fellows on 3 Jan 2010 03:33 On 2 Jan, 22:11, Gerhard Reithofer <gerhard.reitho...(a)tech-edv.co.at> wrote: > The reason for that is, that it uses the ".. index anchor" command which > seems not to be supported from 8.5 on. It's changed name, which seems to be a consequence of the move to being able to clone text widgets. A single model may now have many views, each with its own anchor, and those anchors have to have distinct names within the model. Moreover, we no longer document the existence of the anchor mark (to my surprise). You can get the name of the anchor for the text widget with the undocumented and unsupported [tk::TextAnchor $w] command. Donal.
From: Gerhard Reithofer on 5 Jan 2010 04:37 Hi Don, On Sun, 3 Jan 2010, Donal K. Fellows wrote: > On 2 Jan, 22:11, Gerhard Reithofer <gerhard.reitho...(a)tech-edv.co.at> > wrote: > > The reason for that is, that it uses the ".. index anchor" command which > > seems not to be supported from 8.5 on. > > It's changed name, which seems to be a consequence of the move to > being able to clone text widgets. A single model may now have many > views, each with its own anchor, and those anchors have to have > distinct names within the model. Moreover, we no longer document the > existence of the anchor mark (to my surprise). thanks for that exlpanation. IMHO such "moves" should be better documented as it influences porting and running of existing software. > You can get the name of the anchor for the text widget with the > undocumented and unsupported [tk::TextAnchor $w] command. "Undocumented and unsupported" means that this will be removed "somewhere" with the potential danger of an unexpected removal. This a good idea for trouble shooting (thank's to the foresight of the tcl developers) but I will try to search a final solution. I found another inconsistency in the docs. In the listbox widget the "index anchor" still exists. * Doesn't the same arguments as above apply to that widget aso? In the doce (8.5.4) I read: "Indicates the anchor point for the selection, which is set with the <selection anchor> widget command." * <selection anchor> is a link to tk command "selection" - is that intended? Finally: Does anyone know if ASED is actively developed? I've sent the author a report but did not get any answer. THX * -- Gerhard Reithofer Tech-EDV Support Forum - http://support.tech-edv.co.at
From: Donal K. Fellows on 5 Jan 2010 06:09
On 5 Jan, 09:37, Gerhard Reithofer <gerhard.reitho...(a)tech-edv.co.at> wrote: > "Undocumented and unsupported" means that this will be removed > "somewhere" with the potential danger of an unexpected removal. Actually no. It means "internal use only". It's part of the implementation of Tk, and not the public API. Donal. |