That sounds interesting. For many-to-many relationships it would mean a bit complex data handling but a simplified form with many-to-one or one-to-many it could be possible. I will give it a thought.

And yes, the source code is included with the full version.

Hi,

Thanks for your consideration,

One to many and many to one would be great. Do you know how longit would take to develop it?

Steve.

This will not make it into 6.2 release. It could be available in 6.3 but I need to do some tests first. That would be a time frame of about 2 months.

Can you please describe your use case a bit? That would help me design the feature.

Hi,
Please see below what I was thinking of.

Lets assume we have two or more conference rooms where we need to schedule some events/meetings (Room1, Room2, Room3, with Events A, B, C and D). We have scheduled the following events:
- Room1.EventA
- Room1.EventB
- Room2.EventC
- Room3.EventD
- Room3.EventE
For example, we would like to define and show (with an arrow between events) the following scenarios:
- S1: Room1.EventB can start (is related to) after Room1.EventA is finished.
- S2: Room2.EventC can start after (or is related to) Room1.EventA has started.
- S3: Room3.EventD can start after Room1.EventA has finished.

(the above scenarios are one to one or one to many)
- S4 (not critical; only if possible): Room3.EventE can start after Room3.EventD and Room1.EventB are finished (this scenario would be many to one, however not that important if too complicated)

The important elements would be:
- One to one and one to many relationship that could be modeled in the Event object.
- The graphical representation (with an arrow) of the relationship between events.

The graphical representation of S2 (event related to start of other event, rather than end of other event) is also not very important (arrow can always be from end of dependent event).
S4 is also not very important if it complicates things.
Nice to have: ability to set the color of the arrow for each individual relationship.
Other thingsIm thinking of (but not important): the relationship could have some constraints such as, for S1, Room1.EventB cannot start earlier then half an hour (e.g. needed for cleaning the room) after Room1.EventB has finished.
Thanks,
Steve.

Sorry, correction on the last paragraph, it should read:

Other things I'm thinking of (but not important): the relationship could have some constraints such as, for S1, Room1.EventB cannot start earlier then half an hour (e.g. needed for cleaning the room) after Room1.EventA has finished.

Thanks.

Hi,
Please let me know if this has been considered and made available in release 6.3.
Thanks,
Steve

Did this ever make it in?