I posted this in the JMRI Google group, and the only response was that the print function works. I've tried this on 2 computers, win7 and win10 with the same results.......I've looked at all the preferences for JMRI with no change. It's a VERY simple problem. If I select a loco from and try to print or print preview the selected roster entry, absolutely nothing happens......well, that's not 100% true.....the selection to print the roster 'menus' disappear after about 1/2 second. If I try to print the summary, a print window opens, allowing the print to function. If I try to print preview the summary, the summary page(s) appear, and work as I expect them to work. Windows 10(unfortunately) JMRI 4.6rR81496dc JAVA 1.8.0_111 I have no issues running trains with JMRI & DCC++, or printing from JMRI, just printing selected roster entrties in JMRI. BTW, I hope that the result of the print is the DETAIL of all the CV data for the selected loco, but since I've never gotten it to work, I'm just guessing. The only strangeness I see is in the system console output: 2017-04-27 22:44:23,316 util.prefs WARN - Could not open/create prefs root node Otherwise, nothing appears in error or out of the ordinary. HELP!!!
I haven't used JMRI much but it sounds like a software issue.....you make have to uninstall and re-install....it seems with each new release of JMRI a new set of bugs have been introduced.....Just my thought
This is the second computer I've tried this on, one win7, one win10, with updated versions of JMRI and Java, with the same results..... Looking at the JMRI system console log, I see this every time I try to print the selected entry stuff: InvocationTarget java.lang.reflect.InvocationTargetException InvocationTarget java.lang.reflect.InvocationTargetException InvocationTarget java.lang.reflect.InvocationTargetException Obviously, I tried 3 times...... I sent this info to the JMRI group, but no response yet.
Looks like a known issue https://github.com/JMRI/JMRI/issues/3156 And a fix here? https://github.com/JMRI/JMRI/pull/3166 Jim
Hard to tell......one references issues specifically related to a particular type system/decoder, and the other references a foreign language translation issue. It also references a beta release(odd numbered version) as opposed to a stable release(even numbered version). I tend to NOT use beta code...... BUT, I might try for this issue.
