Xailer & OZ Software

I have a browse and a scrollbox below the browse representing a sort of
workspace. My intent is to allow the user to drag and drop records from the
browse into the scroll box where I represent the record as an icon. So far
so good -- works perfectly *when the table is local*.
The datasource is ADS and the browse is on a table that is quite large in
terms of the number of fields.
When the table is accessed via the Internet, every process is a bit slower
on the browse -- to be expected. The problem is I can actually initiate the
drag and drop process before the browse is finished stabilizing. This is
causing the system to "lock up" in drag mode. I actually have to grab the
record again (repeat the process) or click on the Windows Start button to
"kill" drag mode.
My question is can I disable dragging and dropping until the browse
stabilizes? If so how?
TIA,
Andy

Andrew,
> My question is can I disable dragging and dropping until the browse
> stabilizes? If so how?
I don't understand how is your problem arising. It seems that you are
getting the data asynchronously and this is the source of the problem.
What kind of browse are you using? How are you getting the records?
--
Regards,
Jose F. Gimenez
http://www.xailer.com

I am using a TDBBrowse on the ADS data source referencing a TDbfDataSet and
grabbing up to three fields to display a description under the icon located
in the drop zone of the TScrollBox below the browse. The fields are grabbed
by table reference and field name(s) directly -- ::oTable:FIELD1,
::oTable:FIELD2, etc.
The problem only happens when the drag and drop process is performed
quickly. If I click on a record in the browse, wait a second, then drag and
drop, I don't experience the problem.
What I've discovered since my original post is that the OnBeginDrag event is
not firing right away. If I *very quickly* click on a record then drag
straight down, the cursor is not changing to "Drag Mode" until I move around
a bit -- say back over the browse again. If I don't keep the mouse button
depressed and release it in the "Drop Zone", and then move back over the
browse, *then* it enters drag mode. Since the mouse button is already
released, there is no way to fire the OnEndDrag event. It hangs in drag
mode.
It appears to be a timing thing, which is why I though there was some
processing going on in the browse delaying the drag notification event.
I wish I could show you an example, but it would be difficult to recreate.
"Jose F. Gimenez" <jfgimenez@wanadoo.es> wrote in message
news:[email=44e45712@news.xailer.com...]44e45712@news.xailer.com...[/email]
> Andrew,
>
>> My question is can I disable dragging and dropping until the browse
>> stabilizes? If so how?
>
> I don't understand how is your problem arising. It seems that you are
> getting the data asynchronously and this is the source of the problem.
>
> What kind of browse are you using? How are you getting the records?
>
>
> --
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
>

Andrew,
>I am using a TDBBrowse on the ADS data source referencing a TDbfDataSet and
>grabbing up to three fields to display a description under the icon located
>in the drop zone of the TScrollBox below the browse. The fields are grabbed
>by table reference and field name(s) directly -- ::oTable:FIELD1,
>::oTable:FIELD2, etc.
>
> The problem only happens when the drag and drop process is performed
> quickly. If I click on a record in the browse, wait a second, then drag
> and drop, I don't experience the problem.
>
> What I've discovered since my original post is that the OnBeginDrag event
> is not firing right away. If I *very quickly* click on a record then drag
> straight down, the cursor is not changing to "Drag Mode" until I move
> around a bit -- say back over the browse again. If I don't keep the mouse
> button depressed and release it in the "Drop Zone", and then move back
> over the browse, *then* it enters drag mode. Since the mouse button is
> already released, there is no way to fire the OnEndDrag event. It hangs in
> drag mode.
>
> It appears to be a timing thing, which is why I though there was some
> processing going on in the browse delaying the drag notification event.
>
> I wish I could show you an example, but it would be difficult to recreate.
Yes, I know. But I'm trying to find where the problem is for a while,
without success. I'll continue reviewing, but a small sample could be great.
--
Regards,
Jose F. Gimenez
http://www.xailer.com