All Activity

This stream auto-updates   

  1. Last week
  2. Earlier
  3. Hello. And how did you solve the problem?
  4. We have updated forum engine to the most recent version. If you'll find any problems please do not hesitate to contact administration. Thank you!
  5. GraphX is in the maintenance mode currently. Merged all pull requests and fixing reported bugs.
  6. This is tricky. Group background itself is a simple border, so you can add some mouse handling events for it and store a link that will point that this particular Border is for particular vertex group. So when you drag your Border you can iterate through related vertices and translate them to new coordinates according to the dragged Border. This approach will require a lot of coordinates calculations. As of collapseble groups you can try to implement custom Filter which will hide/show group vertices and add/remove an edge instead of them.
  7. Hi, i've never tried it, but you can try to specify GroupingLayoutAlgorithm as the primary GroupingLayoutAlgorithm parameter so the vertices in a primary group can be layouted by some secondary group.
  8. Hi, I took your Showcase example which is very good and in particular I took in consideration the grouping feature. I'm trying to create a graph with groups where each group can have sub-groups. Do you have an idea how I can reach this goal? Thank you.
  9. Hi, I'm using your library for one of my projects and first of all I would like to thank you for the very good library provided. I your Showcase WPF application you have also created a Grouped layout so that some vertex can be grouped in a limited space and over the graphic area you rendered a rectangle for the group. I would like to use the same grouped layout and add some features I need: - each group can be dragged - each group can be collapsed to an edge (optional) Can you please suggest me how I can use your library / code to make the groups draggable? Thank you, Luca
  10. Hello Tom, sorry for no response. The mail system is out of order again There is no default support for center point, but you can use EdgeLabel for that, as it is placed in the center of the line. Or you can check edge generation code to get the math behind the edge center calculation and then use own EdgeControl implementation for this,
  11. I have seen the update which allows for source and target pointers to be added using the "PART_EdgePointerForTarget" and "PART_EdgePointerForSource" names on DefaultEdgePointers. I was wondering if there is any support for a central pointer. A diode symbol shows roughly what I'm talking about: The actual shape of the pointer is irrelevant since the template can just be given whatever path I want, I am purely asking for placement in the centre of the line purposes. Thanks, Tom
  12. Hello. This is the exact same issue that is described in this GitHub issue that was posted: Reproducible 100% of the time with a single Vertex and 0 Edges on the graph. Is there any light you can shed on the issue further? We are currently using version 2.3.6. If you would like any further information I would be happy to provide it. Thanks, Tom
  13. Thank you for an example!
  14. ??
  15. Thanks, it was helpfull
  16. Hello, please try to set args.MouseArgs.Handled = true
  17. Hello, Find one bug in DoubleClickEvent with dragable vertex. _gArea.VertexDoubleClick += _gArea_VertexDoubleClick; private void _gArea_VertexDoubleClick(object sender, VertexSelectedEventArgs { System.Windows.Forms.MessageBox.Show("1"); } after showing messageBox vertex flyout over screen, and continue follow to mouse. I try to set DragBehaviour.SetIsTagged(args.VertexControl, false); but this didn't help
  18. GraphX for .NET version 2.3.6 is out featuring minor improvements and fixes.
  19. RELEASE 2.3.6 DETAILED CHANGELOG: + Added edge endpoint calculation for rotated vertex that use ellipse, circle and rectangle math shape + Added VertexControl::LabelAttached and LabelDetached events which fires when new label is attached to VertexControl or detached from it + Added new parameter to GraphArea::UpdateParallelEdgesData(Dictionary<TEdge, EdgeControl> edgeList) to be able to specify edges list to parse for parallelization instead of full edge list parse + Added support for object visbility and attachable labels to GraphX serialization data + Added ZoomControl::ResetKeyBindings() method to clear all (incl default) set key bindings + Fixed ZoomControl dynamic content switch to corectly refresh viewfinder + Improved ZoomControl handling with disabled animation + Renamed ZoomControl::IsAnimationDisabled to IsAnimationEnabled and changed the logic according the modification + Renamed ZoomControl::MaximumZoomStep to ZoomStep and updated description + Implemented easy ZoomControl key bindings with BindKey() method and exposed base commands for zoom and pan actions to be able to bind keys for them + Some class refactoring Go to the archive & sources download page NuGet version is also available
  20. Update: now we have one in GraphX for .NET PRO bundle. FYI.
  21. RELEASE 2.3.5 FEATURES HIGHLIGHT: - Added new awesome vertex snapping feature on vertex drag. Many thanks to perturbare for this wonderful contibution! The feature is implemented around DragBehaviour class and is represented in several new settings allowing the drag to be perform around some sort of virtual snap grid. Please read the comment for the DragBehaviour class for detailed info. - Added new feature & example preview in showcase app: graph data filtering. This feature allows you to filter the graph prior to layout generation or relayout based on the pipeline of LogicCore::Filters that are processed sequentially. These filters can modify graph using custom logic. The output graph will be available for interaction along with the copy of the original graph. User then may choose if he wish to revert graph to the original state or apply filtering results permanently. Please read the details at: DETAILED CHANGELOG: - Added Universal Windows Application support and example project - Added StateStorage::ImportState() method to allow state import/export logic between several graphs - Added GraphArea::IsDisposed property that indicated that GraphArea object has been disposed and shouldn't be used anymore - Added GraphArea::CreateNewStateStorage() protected method to be able to implement custom state storage logic for GraphArea - Added ParameterizedLayoutAlgorithmBase::EnsureUniqueRandomInitialPositions property that enables unique random positions generation for layout algorithms. False by default, True for LinLog algorithm. - Added VertexControl::VCPRoot property whcih represents the VCP root container for easier runtime VCP management. To be able to use it you have to define PART_vcproot template element as Panel descendant. - Added new awesome vertex snapping feature on vertex drag (thanks to perturbare) - Added GraphArea::EnableVisualsRenewOnFiltering property which is True by default. Specifies if visual graph should be updated up on relayout method call. - Added methods LogicCore::PushFilters(), LogicCore::ApplyFilters() and LogicCore::PopFilters along with LogicCore::Filters property which implements graph data filtering feature - Added LogicCore::IsFiltered property to identify graph filtering state. If graph is filtered the filter results can be applied or popped back. - Added new porperty EdgeControlBase::HideEdgePointerOnVertexOverlap which can hide edge pointer on zero length edge - Added new property EdgeControlBase::HideEdgePointerByEdgeLength to be able to hide edge pointers if edge length is less than or equal to the specified value. Off by default (0 value). - Fixed LogicCore::GetVertexSizeRectangles() method input params and description - Fixed incorrect edge pointer position on zero length edge - Fixed Avalon Dock interaction which caused strange exception by skipping ZooomControl viewfinder unnecessary refresh pass in some cases - Fixed edge label positioning, now it is more accurate for pathed edges - Fixed LinLog negative energy issue (thanks to Katya) - Fixed one vertex ISOM algorithm exception (thanks to jorgensigvardsson) - Fixed external alg vertex sizes grab logic (thanks to ValentinMarinov) - Made StateStorage class extensible by adding virtual modifiers to methods - Improved algorithm factory logic to avoid graph type cast exceptions in some class declaration cases - Improved calc performance for large graphs that use both OR and ER algorithms - Moved code extensions to GraphX.PCL.Common library thus eliminating the need for GraphX.PCL.Logic for *.Controls libraries - Removed GraphArea::EnableWinFormsHostingMode property as it is not needed any more. The WF checks has been automated. Go to the archive & sources download page NuGet version is also available
  22. GraphX for .NET version 2.3.5 is out on GitHub and NuGet. Grab it while it is hot!
  23. Hello everyone! Today is a wonderful day as we are proud to announce new GraphX for .NET PRO version. You can check the details in the corresponding announce thread. No worries, open source GraphX is still there and completely free as always Also we'd finally launched new web site which will help us to push GraphX product line forward. Check all the new web site as we slowly move to the org domain zone. Going to release GraphX version 2.3.5 soon, stay tuned!
  24. Greetings everyone! Today we proudly announce the release of the GraphX for .NET PRO 1.0.0 version which is planned as our mainstream product! We have a great plans for it so you may expect more features and content to be added soon followed by special highlights. Feel free to read through this announce and ask us questions if you'll have some. So, what's inside? GraphX PRO utilizes open-source GraphX logic core making possible for you to use all the algorithms from this version and all the possible custom algorithms you already have. This also allows us to create new PRO algorithms compatible with open-source GraphX which is still a great visualization tool for templated interactive graphs. Using the PRO version you gain access to a set of new high performance controls designed to handle large data graphs in WPF and UWA environments by utilizing the low-level rendering techniques. These controls allows you to build your graph visualization from scratch skipping the heavy XAML templates and optimize overall performance by using fast and efficient graph object techniques. We also have an performance-tweaked zoom control and additional layout algorithms to play with. For example this highly customizable Radial Layout Algorithm can do the magic with the tree data graphs. Here are some GraphX PRO highlights we have to offer you: New controls for maximum rendering performance you can achieve in WPF. New low-level rendering techniques and plenty of performance optimizations allowed us to create controls better suitable for large data graph rendering and visualization. Also we have more performant ZoomControl to offer. New layout algorithms for better tree graph visualization with different configurable options, including Radial Tree Layout. Expect more algorithms to come soon. Extended support for both FREE and PRO GraphX products including the access to VIP customers area on the forums and guaranteed quick responses on all the questions related to GraphX and derived projects. Priority version updates and feature requests. Access to requested hotfixes in any desirable form and ability to request minor new features with top priority mark. More tools to work with will be added in the future including new algorithms, controls and much more. Special discounts and offers for other services including GraphX-based paid project development and feature implementation! On-demand source code access that includes full GraphX PRO source code sharing and support The Requirements? We want to supply our customers with the best software possible so we have to use modern tools to achieve the best performance and usability . GraphX for .NET PRO software requirements as follows: Visual Studio 2015 Community Edition or higher (for sample projects) .NET Framework 4.5* or higher * Compatibility with other framework versions is a subject for a discussion, feel free to contact us What about the license? GraphX for .NET PRO utilize subscription based licensing model which means you can get new product versions while your license is active and continue to use them even when your license is expired. You won't be able to use new product releases after your license is expired and you have to renew it to be able to do so. Each license is valid for one developer only but if you want to purchase GraphX PRO for many developers you can always contact with the Sales Department. Check the subscription details on our new web-sites: Have Something Special? Sure! We want to thank all our contributors and give them life-time -15% discount for indie and professional bundles if you'd contributed to GraphX before the PRO version release. We appreciate your work and hope to see you working with us on the free open-source GraphX version. Remember, buying our products also helps to push forward our open-source projects! For all the questions regarding the GraphX PRO please contact or use the order form below ** The text given above is not a public offer
  25. Does anyone have an example of rendering a graph in GraphX as a Radial Reingold-Tilford layout?
  26. Hi, to begin with: Thank you for GraphX! I used it already for two mini tools and it just works so fine!!! Now, I am about to create a third tool. In that tool, some graph hierarchy should be included. There are about 10 graphs with about 100 vertices each. The goal is to draw a top level graph with that 10 vertices, 1 for each graph. Then, I want to provide 2 options: (Black boxes = zoomcontrols) 1. Image: The user should be able to click on 2 of that 10 vertices. In a second and third zoomcontrol (possibly contained by 2 vertices in an underlying zoomcontrol... would be a graph in a vertex then), the two graphs are shown next to eachother and the edges which exist between that 2 graphs are shown. The new zoomcontrols also can be 1 instead of 2, but the clear seperation somehow has to be there (a line would be totaly awesome). 2. and 3. Image: The user should be able to click on a vertex or two of them and these vertices are replaced by their containing graphs. Are these things possible with GraphX? What are the steps you would recommend? Are there any things already implemented? Which things do I need to implement by myself at a minimum? ... and a 1000 more questions... Greetings, XDskynet
  27. For me GraphSharp fully supported two-way binding of the Graph object, which facilitated a MVVM style of architecture: public partial class GraphLayout<TVertex, TEdge, TGraph> : GraphCanvas where TVertex : class where TEdge : IEdge<TVertex> where TGraph : class, IBidirectionalGraph<TVertex, TEdge> { ... public static readonly DependencyProperty GraphProperty = DependencyProperty.Register( "Graph", typeof(TGraph), typeof(GraphLayout<TVertex, TEdge,TGraph>), new FrameworkPropertyMetadata(null,FrameworkPropertyMetadataOptions.AffectsRender, GraphChanged)); /// <summary> /// The graph we want to show. Dependency Property. /// </summary> public TGraph Graph { get { return (TGraph)GetValue(GraphProperty); } set { SetValue(GraphProperty, value); } } ... } I don't see how that is possible in GraphX, but rather this concept of "LogicCore". Maybe I missed it but it seems to project doesn't really support MVVM ?
  1. Load more activity