Jump to content

nallath

Team UltiMaker
  • Posts

    4,499
  • Joined

  • Last visited

  • Days Won

    99

Everything posted by nallath

  1. Daid has had very little to do with the new Cura, so he wont be able to answer in depth answers about it. Plugins in itself have little to do with the .json files. The json files are for printer settings. The plugins are much, much more. If you have settings for your plugin, they don't really have a place in the printer json files (because if someone uses a custom printer, the plugin wouldnt work). The disabling of plugins is indeed a bit broken. Its on our list. You should not use values / methods that start with an underscore! Python does not have private / protected members, so we indicate those by starting with an underscore. You should -not- acces _value directly but use .getValue() or setValue() respectively. If you directly change the value no events are passed to other parts of the code (hence it being private).
  2. Have you tried running it in admin mode? If that doesnt work, please post issue on github.
  3. Could you post this on the github? Its a easy fix, but we have a lot of things to do. Makes it easier for us to track it. You can use the arrow keys to move through it. Good one. Could you also post it in a seperate github issue? Same as before
  4. Could you also post this on github? Makes it easier to keep of track of things. I don't see anything in the log file that would explain the crash.
  5. Well if you print something solid and without any thin parts it should be quite allright. But I think it's best not to take the risk.
  6. You are right. We should definately look into this. I believe that the slicing has become a bit slower due to added features on the engine side, but it is weird that the loading is that much slower. Could you create an issue on github? Makes it easier for us to keep track of everything.
  7. Could you run it as an admin and post the log file?
  8. PLA in itself should okay. Not sure about the coloring.
  9. Well, according to google the guy is a community support manager of the UK reseller.
  10. Yeah, but the github issue tracker is a bit annoying. We need a better one.
  11. Hellnaw. Why do people assume the worst? It's a simple time issue
  12. For the moment dropping them here is allright. I've mentioned this to management yesterday already. They are looking into something like this.
  13. Nope, not a known problem. Should be a logfile on windows aswell.
  14. Yeah thats by design. Well, ill look into it later.
  15. Ugh. This is why developers hate mac. Could you also post the log file?
  16. Yup, we specifically design for that as it's easier to test things. We switch back to old versions sometimes to see if something was broken at that point already.
  17. Huh. That is weird. Does the firmware update show when you select that one?
  18. So. Yeah. For the people who want to see how easy it is to make things; https://github.com/nallath/PrintCostCalculator It's very nasty, built this in about an hour. Feel free to improve on this. Trow everything in the folder in a folder inside the plugin folder of cura and it should work.
  19. Allright, thanks for reporting. Its on the list now.
  20. That should be the way to do it. Could you post a bug report on https://github.com/Ultimaker/Cura/issues/?
  21. Oh, wait. We don't use that argument. If it seems that way, i sure as hell did not intend to. People who modified the um are our costumers. We need to support those. You are totally right in saying that those users should have an equal (if not better) Cura experience .
  22. Did you try 15.06.01? Also, what error?
  23. O ye of little faith We meant it when we said that we like people to mess with the internals.
  24. Yeah, whoops. Our bad. I've reported it.
×
×
  • Create New...