[Gtkradiant] [Bug 355] Shader editor crashes radiant

gtkradiant@zerowing.idsoftware.com gtkradiant@zerowing.idsoftware.com
Mon, 22 Apr 2002 19:18:41 -0500


------- Additional Comments From gefdavis@dingoblue.net.au  2002-04-22 19:18 -------
Jumping to the shader line will still work as it has in the past for the
internal editor, and for editpad. But using the same methods with an unknown
editor obviously would work.

I was thinking of adding the ability to use variables in the command box;

[ editor --line $line ]


[ editor --search $shadername ]

When radiant launches the editor it would either replace $line with the line 
number of the shader, or the name of the shader. Although getting the line
number of the shader would probably mean opening it and searching for it the
way it's currently being done with the internal editor.

And of course, this is dependant on the editor supporting similar command line
options, to jump to a line, or initiate a search.

I'm not really convinced (yet) that it's necessary though.

The fix I applied does prevent multiple gtk edit dialogs, atleast... when I
applied it, it did :]

------- You are receiving this mail because: -------
Whoops!  I have no idea!