You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I am adding multiple edges to a graph, and select say source 112, target 116 and click okay, the next time I open the Add Edge dialog, Source will default to 112, but Target will default to the first node in my graph.
Is it possible to have both Source and Target remember my previous selection? Or, failing that, to have neither remember? The inconsistency makes adding multiple edges frustrating. The ideal solution would be a setting, but I can't imagine that's high priority :).
The text was updated successfully, but these errors were encountered:
Sure, adding this to the wishlist.
The explanation is that the feature comes from an old gephi version where repeated edges were not possible, but they are now since Gephi 0.9
Based on commit ecbe7bf#1605 NullPointerException when no attribute is selected in Ranking or Partition
#1469 Impossible to color arcs with a color gradient with 0.9.1
#1477 Import wizard 0.9.1 now showing any options
#1487 Fix - add try/finally logic to wrap graph reentrant locks for layouts
#1536 Add Edge dialog only remembers source index
#1418 Import spreadsheet (csv) The id class does not match with the expected type
#1387 Exception on ranking with column with null values
#1612 Ranking min/max for uncommon types - UnsupportedOperationException: 'commlist' is not a sortable column (int[])
If I am adding multiple edges to a graph, and select say source 112, target 116 and click okay, the next time I open the Add Edge dialog, Source will default to 112, but Target will default to the first node in my graph.
Is it possible to have both Source and Target remember my previous selection? Or, failing that, to have neither remember? The inconsistency makes adding multiple edges frustrating. The ideal solution would be a setting, but I can't imagine that's high priority :).
The text was updated successfully, but these errors were encountered: