Large networks do not render - cytoscape.js

I've been using cytoscape.js extensively to render several networks. It seems to work fine for small networks, however it fails with larger ones (173 nodes and 214 edges).
I had a look at Firebug console and it looks as follows:
TypeError: E._private.edges is undefined
http://localhost/WS/biojs-jmv/biojs/src/main/resources/dependencies/cytoscape/2.0.2/cytoscape.min.js
Line 125
Use of getPreventDefault() is deprecated. Use defaultPrevented instead.
http://localhost/WS/biojs-jmv/biojs/src/main/resources/dependencies/cytoscape/2.0.2/cytoscape.min.js
Line 259
TypeError: H._private.style.shape is undefined
http://localhost/WS/biojs-jmv/biojs/src/main/resources/dependencies/cytoscape/2.0.2/cytoscape.min.js
Line 259
Can it be that I'm I missing something due to configuration? or maybe a library bug?
EDIT:
I updated the library version to 2.0.4. However the problem still persists when rendering large networks. These are the errors that firebug reports:
TypeError: E._private.edges is undefined
http://localhost/WS/biojs-jmv/biojs/src/main/resources/dependencies/cytoscape/2.0.4/cytoscape.min.js
Line 147
TypeError: d._private.style.shape is undefined
http://localhost/WS/biojs-jmv/biojs/src/main/resources/dependencies/cytoscape/2.0.4/cytoscape.min.js
Line 244

The (most likely old) bug seems to be with the style rather than the size of the graph. Have you tried v2.0.4?

Related

TypeError: Cannot assign read only property 'delegatedHandlers' of aurelia-dom-boundary

I've been working on modifying the Aurelia skeleton app, and things have been going along fine. Then I added in two new jspm dependencies, bootstrap-material and aurelia-validation. Once I did that, I started getting the following two errors.
ERROR [app-router] TypeError: Cannot assign to read only property 'delegatedHandlers' of aurelia-dom-boundary
ERROR [app-router] Router navigation failed, and no previous location could be restored.
I cannot get past this. I've tried removing those dependencies, reverting things back to when they were working and I still get the errors. Any idea what could be causing it?
I believe this is just a regression in Aurelia binding library caused by this commit: https://github.com/aurelia/binding/commit/8d33813eb340c2136198916a4a757a2c577f5aab
let boundary = target.domBoundary || document,
delegatedHandlers = boundary.delegatedHandlers || (boundary.delegatedHandlers = {}),
...
I have made a comment, but did not open an Issue.
I rolled back the binding library from 0.8.4 to 0.8.2 until a fix is released.
Edit: they have fixed the issue

Can't display an alert using MessageBox in Sencha Touch 2

In a handler in one of my controllers, I'm running into issues displaying a simple alert message. Using Sencha Touch 2.4.1
Ext.Msg.alert('Status', 'test');
--> "Uncaught TypeError: Cannot read property 'alert' of undefined"
As per these instructions, I added the following require statement: Ext.window.MessageBox to my controller.
--> Failed to find any files for /PATH/FILE.js::ClassRequire::Ext.window.MessageBox
Replaced Msg with MessageBox and removed require statement.
Ext.MessageBox.alert('Status', 'test')
--> "Uncaught TypeError: undefined is not a function"
Ran into the same problem when using .confirm.
Here's the docs - looks like it should work.
Anybody know why it doesn't?
I needed to require Ext.MessageBox instead of Ext.window.MessageBox and had to use Ext.Msg.alert... instead of Ext.MessageBox.alert... though I'm not totally clear on why.
Saw this in the docs: "The framework provides a global singleton Ext.Msg for common usage which you should use in most cases."

Advanced Custom Fields plugin - potential bug?

Good day,
Does anyone know the solution to the following problem?
I have recently set up the Advanced Custom Fields plugin with a custom post template and have been using Gravity Forms to submit post data. Everything seemed to be working fine on a number of posts. However, I went to update a post through the post editor screen and when I clicked on 'update' or 'preview' I got the following error:
Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/uswfeoab/public_html/wp-content/plugins/advanced-custom-fields/core/fields/_functions.php on line 396
This was repeated 8 times before the following error code:
Warning: Cannot modify header information - headers already sent by (output started at /home/uswfeoab/public_html/wp-content/plugins/advanced-custom-fields/core/fields/_functions.php:396) in /home/uswfeoab/public_html/wp-includes/pluggable.php on line 876
I have had a good look at the forums and the ACF website but can't find any troubleshooting for errors relating to the _functions.php file. For reference the line of code on line 396 is $field = array_merge($defaults, $field);
Unfortunately this is way beyond my PHP skills. Any suggestions would be greatly appreciated!
Phew!
The author of Advanced Custom Fields issued and update to Version 4.1.2 today. This has resolved the problem.
Panic over!

dojo errors in Xpages

Using Notes 8.5.3, UP1, I have a long XPage which uses a lot of ExtLib functions. I'm also using TinyMCE and a jQuery table of contents, described here: http://xomino.com/2012/08/26/jquery-in-xpages-14-toc-create-a-menu-to-scroll-to-a-form-section/. When I create a new document it works fine and saves properly. However, once it's opened in edit mode again, I get the following errors in Firebug:
TypeError: node is null
dojo.js, line 14.
Error parsing in _ContentSetter#Setter_view:id1:id9:callback:tabName_pane_6
file "xsp/.ibmxspres/.mini/dojo/.en-us/#Fv&#EOb&#EOd&#EOf&#Ek&#Es&#Ie&#Ig.js", line 82
Error undefined running custom onLoad code: This deferred has already been resolved.
file "xsp/.ibmxspres/.mini/dojo/.en-us/#Fv&#EOb&#EOd&#EOf&#Ek&#Es&#Ie&#Ig.js", line 82
Basically, these errors are preventing any SSJS from being triggered at all. Any suggestions on how to debug this?

MediaElement Uncaught TypeError: Cannot read property 'tagName' of null

I would like to use MediaElement to serve all the videos/formats we have without creating different players. My first attempt was with an .mwv file with throws the error listed in the Title of this post. Next I tried an MP4 which seems to work fine. Then I tried an .flv file which also threw the same error listed in the title.
In Chrome I see "Uncaught TypeError: Cannot read property 'tagName' of null" the console which occurs in mediaelement-and-player.min.js at line 40 but the viewer part of the player doesn't display at all. In Firefox I see "TypeError: d is null" in the console at the same line number but the viewer part of the player DOES display and it says: "Video format or MIME type is not supported". The MediaElement documentation indicates that those types are supported but I can't seem to get them to play.
Either I mis-configured the player or I am passing the wrong content-type (I tried several) or this is a bug. I saw a similar post but the solution posted there was a little vague. I am going to try different files, formats and mime types to see if I can sort out the issue but I think this is a code problem. Ha anyone else been able to play flv or wmv files with mediaElement? Was there a trick to making it work?
I missed a step (or a directive) in the configuration. The 'tagName' error had to do with the content type I was using and was not defined in Glassfish. The reason that nothing was playing was that I forgot to list the class as "mejs-player" in the video tag.
Cleaning up those two things got the player working.