开云体育

Rick, If you upload your TimeTableData.xml file to the ProblemsBeingWorkedOn folder, I can see if it a data issue or a program issue. I suspect that it is a program issue since I did not take into

Updated to 4.16 from 4.11.6 and receiving panel load errors.? Also tried reverting to 4.14 with same results. Uninstalled and went back to 4.11.6 but now it will not load any panels without

I have created a new layout in the timetable tool.? In this layout I have multiple segments which include a 'Main' segment and a 'Reading Branch' segment.? I have created all the stations and set

I realized my reply wasn't clear as to which error I was seeing. I was seeing this: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (default-cli) on project jmri:

Thanks, Dan. Tried steps exactly as you describe. Ant build works fine and PanelPro starts. But I still get the same error when subsequently I try to run the "Maven Build" "JMRI PanelPro" from the

When I experience this problem, it is due to the meta-data not being created correctly.? One way to fix is to use ant, under targets, do a realclean, followed by PanelPro.? After the ant builds

Steve, I have uploaded a modified version of your previous file. I was using 4.17.3. /g/jmriusers/files/ProblemsBeingWorkedOn/dsand/bestFarfelu15J%20DS.xml This has valid discovered

Greg, did you ever get this sorted? I get the same error trying to compile/run with the maven build. The ant build and run works fine.

Hi Dave Just to follow up. I tried it again with the latest JMRI version without luck. I rebuilt the whole layout from scratch using different names for blocks, signals and turnouts and hit the same

That is what I use when I run JMRI, a apple wireless trackpad. Don’t like trackpads but it works. Jim

Jim, Could also be a faulty MM. Dave in Australia

Jim, Have you disabled the side squeeze sensors on the Mighty Mouse? System Preferences->Mouse. My memory is that they default to Exposé. First thing I do when using a MM. Dave in Australia

Jim: Misread that Mighty Mouse v. Magic Mouse... sometimes too clever names... I'm thinking now that the interaction of the three serial I/O drivers + Java with the mouse driver might indeed be

It is a wired mm. It is a 2014 mini that you could still upgrade the ram on. It has had the hard drive replaced with a ssd and is the quad core i7. Very fast machine. Running the latest of all apple

Jim: Mac Mini and wireless human input is all Bluetooth so if keyboard and track pad work MM should be happy... Does it work as advertised when Java/JMRI is not running? Is it newer MM2? From you Mac

The screen keeps going in and out of expose. Slightest touch sets it off. Works fine on everything else except JMRI and JAVA. Jim

Jim, What doesn’t work with the mighty mouse? Is it the nipple, 3D scrolling? as these are managed at system level I’ve never had any issue with JMRI and the mighty mouse so don’t think its a

Upgraded from 4.15.8 to 4.17.3 I am using 3 Keyspan USB to serial converters on a Mac I am using keyspanUSAdrvr 4.0b4 because of upgrade to Mac 10.14 One connection is CMRI with 9 SMINIS One

Jim: On re-reading perhaps I should have said "no" because you asked if the DP labels REPLACED the standard decoder ones. My "yes" answer was to the question ARE THEY THE SAME which is not what you

Jim: DP function defaults depend on the decoder selected so for many/most/all decoders "yes" F1 bell etc. But don't forget DP is just a way of setting CVs so what actually happens when you press a