DATAGRID dgDragImageIndex problem

Jan Schenkel janschenkel at yahoo.com
Wed Jul 28 15:25:24 CDT 2010


Ok, I think I have figured it out after studying the script of the DataGrid behavior button.

Quartam Reports uses the templateImage to create the image control for the report. Then, the DataGrid tries to find an image 'dgDragImage' in the datagrid group control- and when it doesn't find this image, it promptly creates a new image. 

But at that point, the templateImage is still preset with the last settings from Quartam Reports. Now, we can debate whether or not the library should cleanup after itself, but the safest solution is probably to call 'reset the templateImage' before creating the dgDragImage control.

So when I changed Josep's drag-drop datagrid script to call 'reset the templateImage' before setting the dgDragImageIndex, everything worked correctly (in Rev 4.0/4.5 on MacOSX anyway).

No need to file it in the Quality COntrol Center - Trevor's already on top of it :-)

Jan Schenkel
=====
Quartam Reports & PDF Library for Revolution
<http://www.quartam.com>

=====
"As we grow older, we grow both wiser and more foolish at the same time."  (La Rochefoucauld)


--- On Thu, 7/22/10, JosepM <jmyepes at mac.com> wrote:
> 
> Sended... :)
> 
> --- On Thu, 7/22/10, Jan Schenkel <janschenkel at yahoo.com> wrote:
> > Hmm, I can't really think of a reason
> > why the Quartam Reports preview window would interfere with
> > the dragImage of a datagrid. Could you email me a minimal
> > reproducable test case, so I can debug it?
> > 
> > TIA,
> > 
> > Jan Schenkel
> > =====
> > Quartam Reports & PDF Library for Revolution
> > <http://www.qiartam.com>
> > 
> > =====
> > "As we grow older, we grow both wiser and more foolish at
> > the same time."  (La Rochefoucauld)
> > 
> > 
> > --- On Wed, 7/21/10, JosepM <jmyepes at mac.com>
> > wrote:
> > > 
> > > Hi Trevor,
> > > 
> > > The point of change is when launch some report with
> > the
> > > preview option, not
> > > the Quartam Report app, and the image replaced is one
> > > inside the report.
> > > 
> > > For if this can help to solve this strange issue...
> > > 


      




More information about the use-livecode mailing list