Dion Moult
Dion Moult
FYI models from 12D use nesting so users have been reporting that pipes don't show up in Revit. There is now a patch for this in the Blender BIM Add-on.
@khellandgs this seems to be the same comment I made in March 7?
Also bumping this that duct currently has shapes for RECTANGULAR, FLATOVAL, ROUND, whereas pipes assume all pipes are circles which is not true (e.g. many downpipes are rectangular).
@machinedgod that's a great solution! I can confirm it works on my .ics file coming from some Microsoft platform somewhere. Can I ask why doesn't calcurse just implement this feature...
+1. Something like smart keywords would be great too. For example, typing "ddg foo" will search duckduckgo with the string "foo", just like how it works in elinks.
java.lang.RuntimeException: uncategorized problem while processing https://transportnsw.info/web/XML_TRIP_REQUEST2?outputFormat=XML&language=en&stateless=1&coordOutputFormat=WGS84&sessionID=0&requestID=0&coordListOutputFormat=STRING&type_origin=coord&name_origin=151.067368%3A-33.781010%3AWGS84&type_destination=coord&name_destination=151.067127%3A-33.781026%3AWGS84&itdDate=20190104&itdTime=1653&itdTripDateTimeDepArr=dep&calcNumberOfTrips=6&ptOptionsActive=1&itOptionsActive=1&routeType=LEASTTIME&changeSpeed=normal&includedMeans=checkbox&inclMOT_0=on&inclMOT_0=on&inclMOT_1=on&inclMOT_2=on&inclMOT_3=on&inclMOT_4=on&inclMOT_5=on&inclMOT_6=on&inclMOT_7=on&inclMOT_9=on&inclMOT_8=on&inclMOT_10=on&trITMOTvalue100=10&locationServerActive=1&useRealtime=1&nextDepsPerLeg=1&inclMOT_11=on&inclMOT_13=on&inclMOT_14=on&inclMOT_15=on&inclMOT_16=on&inclMOT_17=on de.schildbach.pte.AbstractEfaProvider$7.onSuccessful(AbstractEfaProvider.java:2039) de.schildbach.pte.util.HttpClient.getInputStream(HttpClient.java:233) de.schildbach.pte.util.HttpClient.getInputStream(HttpClient.java:163) If you want to report this error, please report it to public-transport-enabler directly and attach a screenshot.
That's a fresh copy-paste. It seems OK if I visit the website directly. Could it be a problem on Transportr's end?
I should mention that the link in the screenshot to the public-transport-enabler issue tracker doesn't work either :) the URL is wrong.
Is it possible for any dev to replicate this issue? I assume then they can get a stack trace :)
Happy almost anniversary bugreport! I am able to trigger this still. But an update: I now see that if I use the search fields, I can get a route successfully....