[Openroad-users] Clickpoint problems with SegmentShape

[David Tondreau]

Jim,

We are discussing the implementation of a polyline for the next release
of
OpenROAD (the open source release).  Joe Kronk mentioned it on the last
VIP
webcast.  A polyline system class would allow the 4GL developer to
implement
any vector shape and would make creation of almost any kind of chart
possible.

If you would like to have input into the definition of this
functionality,
drop Joe a line.  Part of the edict we are under from management as we
go
down the open source route is to do much more (all?) of our planning and
design in the open as part of the community process.  This won't happen
overnight but we are already engaging partners on specific projects.
These
partners are aiding in the design, implementation and/or testing of new 
product features.  Look for more transparency in the process to evolve
over time.

Regards,

David

David Tondreau
Architect, Ingres Corp.
01-703-738-4811 (w/m)
david.tondreau at ingres.com


-----Original Message-----
From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Antill, Jim
Sent: Tuesday, October 16, 2007 6:17 AM
To: openroad-users at peerlessit.com
Subject: [Openroad-users] Clickpoint problems with SegmentShape


Hi,

I'm having quite a bit of difficulty accurately detecting a
childclickpoint
event on a segment shape within a composite and was wondering if anyone
else
had found a solution to similar problems. I'm using OR4.0 .

The problem seems to be that when a childclickpoint event is detected
the
formfield itself doesn't pick the event up. Rather the coordinates of
the
clickpoint are taken and the array of fields within the composite gone
through to find the first field that contains the clicked on position.
That
works pretty well for rectangular shapes (as most OpenROAD fields are).
However, in the case of segment shapes it seems that a box is formed
from the
start and end points and points within this are checked rather than
points
that fall on the line itself. So if you have segments that are close to
each
other, but not overlapping, the wrong segment is invariably picked up. I
have
some example code here that demonstrates the problem. If anyone is
interested
I'll post it up.

More worryingly this can result in code being fired in error as any
clickpoint code behind the segmentshape that OpenROAD mistakenly thinks
was
clicked is then executed.

As you can imagine this leads to severe problems when doing things such
as
Pie Charts which isn't an unusual requirement. I have tried to use
MSGraph in
the past but had a number of issues with it's behaviour with OpenROAD
(mainly
due to sizing). This might be improved with OR2006 I guess.

So, my questions are: Does anyone know whether this behaviour will be
changed
in OR2006, will we be given better drawing tools in the near future e.g
draw
a filled arc in a circle etc. and has anyone a favourite alternative to
graphing that allows interaction between the graph and OpenROAD?

Thanks for any advice.

Regards,
Jim

************************

This message has been delivered to the Internet by the Revenue Internet
e-mail service (OP)

*************************

________________________________________________________________
OpenROAD-Users mailing list

You can maintain your subscription here:
http://www.peerlessit.com/mailman/listinfo/openroad-users

To unsubscribe click on this link
mailto:openroad-users-unsubscribe at peerlessit.com&subject=unsubscribe

To subscribe click on this link
mailto:openroad-users-subscribe at peerlessit.com&subject=subscribe