开云体育

I can easily create turnouts, sensors and blocks but I can't delete them from their Panel Pro tables with jython. The only method I found while browsing the class structure was dispose() and that had no effect. So far I am only using the simple jython classes ( if I have the nomenclature correct) in statements like turnouts.newTurnout(...) .

--

-Ralph

Can I ask why you would want to remove a turnout dynamically?

I like the symmetry of constructors and destructors. I do understand that automatic garbage collection was a primary justification for Java (yet another programming language), and destructors per se do not exist. Fortunately I found deleteBean() and now can blow away all kinds of stuff.

?

Anytime I have to deal with a new programming or scripting language (currently python/java for JMRI) I am reminded of a truly classic article from 1982. My hard copy that I have had since then is titled "Real Programmers Don't Write Pascal." At the time I was a proficient Fortran 66 user, and yes did use punch cards and JCL on IBM 360/370 mainframes and had worked at Sandia National Labs, so I appreciated the tongue in cheek humor. The article can still be found, https://en.wikipedia.org/wiki/Real_Programmers_Don't_Use_Pascal.

--

-Ralph

Ralph,

?

In agreement with the previous posters on this thread, the concept of dynamically removing track seems like something for a bad horror movie.? Really?

?

However, since Sensors and Turnouts are both bean objects, the postings /g/jmriusers/topic/108527414#msg234620 "Deleting Objects in Scripts" seems like it has the information requested.? Of course, the "why?" was not answered there either.

?

Happy destruction.? But keep it contained to your layout.

?

Cliff in Baja SoCal

I note that scripting and Java is listed in the layout automation section of the JMRI website. Perhaps that is why I am sensing discomfort with regard to what I thought was a simple programming question. No I do not intend to run scripts to operate an actual layout that would involve deleting turnouts or anything else. However, I do find that working with the layout editor and Panel Pro in general is frustrating and I am exploring alternative approaches to getting things done. For example I have used the AnyRail scripts to set up initial panels and found that the exported file from AnyRail has seemingly added tiny track segments with the incorrect block assignments around turnouts and that requires painstaking editing before signal masts can be placed easily. Additionally, part of the AnyRail to JMRI process involves using a script to place sensor icons. It places them directly over a track segment selection circle, making it almost impossible to select the icon to move it. I have not looked yet but have to believe it is relatively easy to iterate over the sensor icons and change their coordinates. Probably easier to edit the existing script for my own use to permit an offset when adding the sensor icons. But it might turn out to be useful to know how to delete things as part of an editing procedure and that is basically all I was thinking about.

--

-Ralph