SimpleGraph 2.6 released!

[Kambiz]

http://www.delphiarea.com/products/simplegraph/

v2.6 is the last release for 2.x update serries.

Probably there will be some fundamental changes in the next release of SimpleGraph.

Please post here whatever you wish for the next release of SimpleGraph, and of course bugs you may find in the current release.

Cheers

[HPW]

Kambiz,

Thanks again for the usefull additions.

It is difficult to keep in touch with your pace!

Time to port.

[HPW]

After compiled with 2.6 I set explicit to cmViewOnly,
but now I can still click on Nodes and edit.
This was not the case on <2.6.
Anything changed there?

[HPW]

Some more obeservations to this:

Mouse access is on on cmViewOnly, so I can
select, drag size and edit the nodes.
But keyboard action is disabled.

??

[Kambiz]

Always there's at least one more bug!

[Kambiz]

I fixed the bug, and uploaded the update.

Thank you!

[HPW]

Thanks for the quick fix!
Will try now.

Edit: works fine again!

[kokkoras]

> ObjectAtCursor: TGraphObject (Read-Only)
> Specifies the last object found under the mouse cursor.

Could you please clarify what do you mean by "last object"?
Is it the one on the top of the pile or the one at the bottom?

Thanks

[Kambiz]

> ObjectAtCursor: TGraphObject (Read-Only)
> Specifies the last object found under the mouse cursor.

Could you please clarify what do you mean by "last object"?
Is it the one on the top of the pile or the one at the bottom?

Thanks

The value of property sets inside the mouse events. And, of course, it's the top most object.

[kokkoras]

Probably there will be some fundamental changes in the next release of SimpleGraph.

Anything particular in mind?

Please post here whatever you wish for the next release of SimpleGraph, and of course bugs you may find in the current release.

1. Grouping support.
2. Undo/Redo support

[Kambiz]

What do you think about merging:

Code: Select all

TGraphLinkOptions = set of (gloFixedStartPoint, gloFixedEndPoint, gloFixedBreakPoints);
TGraphNodeOptions = set of (gnoMovable, gnoResizable, gnoShowBackground);
TGraphGroupOptions = set of (ggoMovable, ggoResizable);

in to a single set of options as:

Code: Select all

TGraphObjectOptions = set of (goLinkable, goSelectable, goMovable, goResizable, goShowCaption, goShowBackground);

In this case, for Links we have:

Code: Select all

goReszable <=> not (gloFixedStartPoint, gloFixedEndPoint, gloFixedBreakPoints)

[kokkoras]

It seems more compact that way.

>> TGraphGroupOptions = set of (ggoMovable, ggoResizable);

So, you started!!

Are GraphGroups virtual objects (that is, with no other visualization apart from their member objects)? It would be nice (well, at least for me ) to be able to visualize it. For example, have a GraphNode associated with it.

In a second thought I think it serves the group idea well, because you can use it to establish move, resize, background coloring, ect. The only requirement is to give the group object mouse priority. Objects belonging to a group should not be selectable (although modern apps - OfficeXP - allows direct selection inside the group). I am not sure though if Groups should be handled in a special way from the core lib. Have you make up your mind?

EDIT: One question that puzzles me regarding groups is the relationship with its member objects. Where to put the associations? Store the member IDs in the group OR store the groupID in each member object?

[Kambiz]

Althought a Group is a TGraphObject, but it doesn't draw its client.

Each group has a Members property as type TGraphObjectList. Also, each object has a Group property as type TGraphGroup.

Each group treats as a single object, and its members does not appear in Objects property of SimpleGraph. The members are accessible only by Members property of the group.

The objects within a group are selectable but they will be treated as locked. Therefore, the group members cannot be moved or resized individually.

As well as other object types, a new group class can be derived from TGraphGroup and be registered in the control.

[kokkoras]

Althought a Group is a TGraphObject, but it doesn't draw its client.

So, client objects of a group are absolutely positioned on the SimpleGraph canvas (NOT relative to the Group position). Also I understand that client objects of a group are painted like before. Correct?

Each group has a Members property as type TGraphObjectList. Also, each object has a Group property as type TGraphGroup.

That's cross refference. No problem. It's flexible.

Each group treats as a single object, and its members does not appear in Objects property of SimpleGraph. The members are accessible only by Members property of the group.

How about having an All list as member of the TSimpleGrph that has pointers to any object, apart from the groupNodes? I have seen this approach in DOM handling of TWebBrowser.

The objects within a group are selectable but they will be treated as locked. Therefore, the group members cannot be moved or resized individually.

That's nice. That way we can pop-up a properties dialog and alter some properties (except X, Y, W and H - maybe).
Regarding positioning and resizing, is it hard to allow then and constrain them to the group object's bounding rect? (Are the old/current move and resize commands constrained?)

As well as other object types, a new group class can be derived from TGraphGroup and be registered in the control.

Thats true!

[Kambiz]

Althought a Group is a TGraphObject, but it doesn't draw its client.

So, client objects of a group are absolutely positioned on the SimpleGraph canvas (NOT relative to the Group position). Also I understand that client objects of a group are painted like before. Correct?

"NOT relative to the Group position" is wrong. Seems you wrote this phrase before reading my entire post.

P.S. I mean ZOrder is relative. X and Y Positions are absolute.