New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Script error with Report Window #4
Comments
Same with me. Win 7, dynamo 1.1 for Revit. |
@dietervermeulen and @josols here's a link to Mandrill Primer that explains how the data needs to be structured for Parallel Coordinates Chart. https://konradsobon.gitbooks.io/mandrill-primer/content/parallelCoordinates.html Here's your sample re-worked to match that structure. Good luck! |
can you do two things for me?
|
PS: Executed in Dynamo Studio 2017 |
OK, so the script looks just fine, and if the file exists I can only suggest one more thing. Please try closing Studio and firing it up in Dynamo Sandbox. That's the version that I am testing on. I did run into this issue before when firing up Mandrill from Revit, but found no solution yet. Here's a link to my conversation with Dynamo dev team: DynamoDS/DynamoRevit#1143 Ps. I tested that file trying to launch it from Dynamo inside of Revit and it fails for me as well. I still have no idea why it won't work when launched from within Revit but works just fine in Sandbox. |
Does not work in any of the versions: Revit Dynamo, Dynamo Sandbox or Dynamo Studio (the last one is in fact now also the Dynamo Core which is the same as the Sandbox.)... |
Which is exactly the version I use :-) |
OK, I will keep this issue open, but I am not sure how I can debug your issue without being able to re-create it. I am on Win7 at work and Win10 at home so operating system is probably not an issue. I guess that it has to do with what app owns the window which in turn sets the context for data. I will try looking at that if I hear from more people that they can't get it to work on their machines. |
The same happens with me. |
@ksobon the problem can be the path? Because the file is on the correct place. |
@ricardo7cordas that's not an issue. That's an error that is being thrown for every exception that happens inside of d3.js I checked that the path is fine, and it was escaped inside of code so the actual path doesn't have %20 in it but a space. Please see the TXT attached by @dietervermeulen in above comment. I have no idea what causes that error and I have very little to go on here. Sorry. |
Ok @ksobon . Thanks for your effort |
Hi Konrad. I am unfortunately experiencing the same issue with all charts. I've tested with sandbox and revit on win7 enterprise and win10 home, and got the script error with every setup (d3 is undefined). Since you can't recreate the issue, I thought it might be some weird reference issue or something, and figured I'd try building the package from the source. |
I think I know what the issue is. I am using a WebBrowser control to render these charts and in all its greatness its no different than using an IE7 which might or might not work on each individual person's computer depending on their own setup. Also, i found that WebBrowser control usually has trouble and unpredictable behavior when it comes to using local resources (d3.js) and it frequently denies access to these resources. I need to implement a different web browser and preferably one based on Chrome or FireFox. Currently I am looking into things like CefSharp, Awesomium and EO.WebBrowser. I will let you guys know when I have figured out which of these will fix the issue here. Thanks for the patience. |
Great job! Looking forward to trying it out |
Sounds good to me too, as long as their are no legal issues with this use of the license? Op 27 sep. 2016 om 17:40 heeft Konrad K Sobon <notifications@github.commailto:notifications@github.com> het volgende geschreven: OK, I tested my assumption using a EO.WebBrowser which uses Chrome and it turns out that I was correct. I can get my charts working now, in Sandbox and Revit without any errors. It turns out that It was about security restrictions and how browsers disable any website javascripts from accessing local files. What is possible with the EO browser is that it allows you to disable that and access the local d3.js files. Also it would mean consistency since it will no longer be dependent on what IE browser is installed on user computer since EO chrome browser would be distributed with Mandrill as a DLL file. There is one small issue though. EO charges $700 for a license. Without it, it works but will show a little window in the corner of the screen: It's not actually embedded in the chart window, and you can move your chart to a different screen so its not a big deal, but still just slightly annoying. Let me know what you guys think. I will post an update with this new browser solution for you all to test. Feedback is welcome. You are receiving this because you were mentioned. |
I would rather purchase the license and then it states that its perfectly legal to ship their DLLs with the application. I am sure its OK to ship the free version as well but the pop-up is annoying. I need to raise some founds for this. I don't think I want to start investing $$$ and time into my Open Source projects... |
kickstarter |
Ricardo, try the chrome window node. This one didnt change. |
Now i need to somehow solicit $700 to make the small window in bottom right corner go away. Lol. Glad it works for you. |
We will ask for donations. I do advertising here with the guys from Brazil if necessary. And also contribute with $$$. This is an amazing job. |
I was thinking about starting a small fundme.com project so people can contribute. Lol. I will set something up. I need to fix a few more bugs and i will set that up. Thanks for the offer! |
Let's do it. |
Works fine now ! Great job Konrad. |
Here's a link to a fund if you guys want to contribute: https://funds.gofundme.com/dashboard/mandrill Thanks! |
When running the script with the Report Window, I get a Script error (see screen shots) and at the end the window is empty.
The text was updated successfully, but these errors were encountered: