For some reason the default behaviour in this package is to allow users to move the trees around as they please.
How do you disable grabability?
I'd also accept an answer which suggests a different tree-graph package that looks nice and doesn't allow users to drag it around the screen.
The package is hosted at:
https://github.com/bkrem/react-d3-tree
And here is an example in CodeSandBox:
https://codesandbox.io/s/yq86mj80zx?file=/src/index.js
Related
For almost every page I open in Firefox, I see this error in the Console of the developer tool bar:
(!) The Components object is deprecated. It will soon be removed.
The source is the html page. It happens with pages I create, but also on many common websites.
I found this documentation on Components object on MDN web docs, but that does not clarify a lot. Note that even that page shows this message(!)
It looks like a warning, but according to the Console filter, it is an error.
My main questions are:
Is this something for me, as a developer of the page reporting this, to solve?
If so, how do I go about that?
I am not aware of any problems as a result of this. For now, that is.
I have seen this for over a year, maybe longer. I mostly ignore this, but every now and then it starts nagging me again. I don't want my code to break suddenly and would like to get rid of this message obscuring other messages.
This is not for the developer of the page to solve.
While biking back home, a possible cause popped up in my mind: could one of the add-ons I use cause this and yes, that appears to be the case.
I restarted with disabled add-ons and the message was gone.
Then I enabled them one at a time and the culprit is
Selenium IDE.
A bug report on this issue was closed with Won't fix, with the message:
This error will resolve itself when we move to a native app later this year.
In a MozillaZine topic of 2012, it is explained how it could have been solved.
The first one is just a warning that the addon is using "Components"
directly, which won't necessarily always be possible when using the
Add-on SDK. (The preferred way to do it is to access the aliases for
Components.classes and Components.interfaces and such that the SDK
provides by requiring the "chrome" module.) It shouldn't be a problem
right now, but might become one in the future.
it happened for me after installing Selenium plugin in my FireFox.
Been trying to find similar component, have not yet find one. I want a component that basically able to expand an object to a panel next to it just like MacOS's file system. I wonder if anyone already know such exist and found it? Since I have no idea what this effect's name to start search from .
I am trying specifically, looking for a reactjs / pure js based visual component does it.
This type of view is known as Miller columns.
You're looking for NSBrowser.
It's kind of deprecated (Apple has never updated it to use views, so you still have to use cells). It's also idiosyncratic and has lots of undocumented behavior.
Enjoy ;)
Coming from eclipse, I am used to be able to move methods around in a file by simply dragging them around in the structure view (called overvew in eclipse).
I have noticed that it is not possible in RubyMine by default. Is there a way to enable it?
If not, is there a feature request for this?
All I have found yet is this: http://youtrack.jetbrains.com/issue/RUBY-2987, http://youtrack.jetbrains.com/issue/RUBY-9672 which considers only moving methods between classes,
Thank you
disclaimer: This started a copy of my attempt to get an answer on the JetBrains forum.
As #LazyOne said in his comment, there is an open feature request for drag&drop inside the structure view : http://youtrack.jetbrains.com/issue/IDEABKL-71.
It has been created in Feb 2005 and is not scheduled for any upcoming version, with only 11 votes so far, so no need to get your hopes up.
I'm trying to
Install-Package NHibernate
but I'm getting "Package ... could not be found". If I open the PCM-options, the list of available sources is filled, but the green OK-symbol isn't there.
Can I use an alternative source different to the MS-Links-ID 206669 which is the default source in VS?
I had a similar problem last night. The two LinkID values I had were:
206669 and 19913
Meaning that the URL I pass into the Settings dialog were:
https://go.microsoft.com/fwlink/?LinkID=206669
https://go.microsoft.com/fwlink/?LinkID=19913
The 19913 did not yield anything in the list of packages available. I think this number came when I installed the package a few weeks (months?) ago and gave up the first time.
The 206669 seemed to work. I could see the expected packages, but I could only install some packages, not all. For example, I could get Castle, but not Log4net. I could get AutoMapper, but not RestSharp. The ones that failed simply said "operation timeout".
I'm glad that I'm not the only one to see these issues - I did not see anything about this in the FAQs or documentation.
It seems that the LinkID and that URL are a weakness in the framework. I would like to see more discussion about that these values mean, and why there seem to be now at least 3 different values to use. How about a more clear link like www.nuget.com?
And how about a message showing more clearly why an operation times out on one package but not another.
NuGet has great promise, and many people swear by it. I want to get on board, but hiccups like this can really stop people from adopting it.
Cheers,
Daniel
Firefox 4 comes soon (ok, next year ;)) and there is a Firefox plugin to sync your bookmarks etc. with Firefox 3.whatever .
I would like to know if anyone has a comprehensive, up-to-date tutorial to integrate Firefox Sync into your own plugin? Or any idea regarding this?
I mainly followed this official "tutorial" and also this blog post, but the information seems to be slightly outdated.
For example, the object is not called Weave anymore but Engines and the weave.engines. preference became services.sync.engines.. I played a little with all the mentioned options, but it does not seems to work (and my plugin does not show up in list where you can select what to sync).
I assume that the Tracker and Store classes are fine, the main problem is to register the engine...
The ClientAPI tutorial you mention is definitely the way to go. I updated it recently so if something's not working, please let us know so I can fix it in the docs. Wladimir's blogpost is definitely quite old and contains some outdated information. We will also make changes to some parts of the API in the upcoming beta releases, so be prepared for some flux...
The Weave namespace is still the canonical way to access Sync related APIs from UI code. It exposes components such as Weave.Service and Weave.Engines. You can import it via Components.utils.import("resource://services-sync/main.js"). If you want to implement your own engine, you'll have to import the actual underlying modules, though (all listed in the ClientAPI tutorial). The tutorial also describes how to register your custom engine implementation. Once it's registered, it won't automatically show up in the preferences UI, though. I suggest building your own UI that flips the services.sync.engine.YOURENGINE pref in your add-on's preferences.
Out of curiosity, what kind of data are you trying to sync?