[RBASE-L] - Re: Flickering images

[Michael J. Sinclair, MD]

Done! I did give you credit for the idea.

Thanks for your support!

Mike

-------------- Original message from "MikeB" <mbyer...@byerley.net>: --------------


> No.. Go ahead and request it yourself. I do however see merit in the ReCalc
> Variables vVarName idea. So you might fire up a properly structured request
> for both items.
>
>
>
>
> ----- Original Message -----
> From: "Michael J. Sinclair, MD"
> To: "RBASE-L Mailing List"
> Sent: Friday, March 27, 2009 12:49 PM
> Subject: [RBASE-L] - Re: Flickering images
>
>
> >I think that is a great idea Mike. Would you like to ask for the
> >enhancement?
> > Mike Sinclair
> > -------------- Original message from "MikeB"
> > : --------------
> >
> >
> >> This would be much easier if it were addressed using the Standard Image
> >> control. It needs to be enhanced to include:
> >>
> >> Property CompIdOfImageCtrl 'Picture->Load' .vPicPathName
> >> Property CompIdOfImageCtrl 'Picture->Clear' .vPicPathName
> >>
> >> This would'nt be affected by the Recalc issue and is a sensible
> >> enhancement
> >> for the control.
> >>
> >>
> >>
> >> ----- Original Message -----
> >> From: "Emmitt Dove"
> >> To: "RBASE-L Mailing List"
> >> Sent: Friday, March 27, 2009 9:27 AM
> >> Subject: [RBASE-L] - Flickering images
> >>
> >>
> >> > Mike,
> >> >
> >> >
> >> >
> >> > One final set of thoughts:
> >> >
> >> >
> >> >
> >> > Where the images are located relative to where your app is running, and
> >> > the
> >> > size of the images will impact the display speed. So if you're running
> >> > the
> >> > app locally but the images are on a network somewhere, delay in display
> >> > is
> >> > inevitable. Try co-locating the images with where the app is executing
> >> > by
> >> > either putting the images on the workstation or run the app on the
> >> > server.
> >> >
> >> >
> >> >
> >> > Also, if you're using high-quality jpegs, try a lower quality or
> >> > resolution
> >> > to reduce file size and therefore reduce the time it takes to
> >> > load/display.
> >> >
> >> >
> >> >
> >> > Another possibility, and I have to say this is a stretch, would be to
> >> > store
> >> > each image in its own temporary table and use db images instead of
> >> > variable
> >> > images. That way, when the image changes, you update the table then
> >> > issue
> >> > a
> >> > PROPERTY TABLE tablename 'REFRESH' to refresh just the one table and
> >> > therefore just the one image.
> >> >
> >> >
> >> >
> >> > Emmitt Dove
> >> >
> >> > Manager, Converting Applications Development
> >> >
> >> > Evergreen Packaging, Inc.
> >> >
> >> > emmitt.d...@everpack.com
> >> >
> >> > (203) 214-5683 m
> >> >
> >> > (203) 643-8022 o
> >> >
> >> > (203) 643-8086 f
> >> >
> >> > emmitt.w.d...@comcast.net
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >
>
>
> --------------------------------------------------------------------------------
>
>
> I think that is a great idea Mike. Would you like to ask for the
> enhancement?
> Mike Sinclair
> -------------- Original message from "MikeB"
> : --------------
>
>
> > This would be much easier if it were addressed using the Standard Image
> > control. It needs to be enhanced to include:
> >
> > Property CompIdOfImageCtrl 'Picture->Load' .vPicPathName
> > Property CompIdOfImageCtrl 'Picture->Clear' .vPicPathName
> >
> > This would'nt be affected by the Recalc issue and is a sensible
> enhancement
> > for the control.
> >
> >
> >
> > ----- Original Message -----
> > From: "Emmitt Dove"
> > To: "RBASE-L Mailing List"
> > Sent: Friday, March 27, 2009 9:27 AM
> > Subject: [RBASE-L] - Flickering images
> >
> >
> > > Mike,
> > >
> > >
> > >
> > > One final set of thoughts:
> > >
> > >
> > >
> > > Where the images are located relative to where your app is running,
> and
> > > the
> > > size of the images will impact the display speed. So if you're running
> > > the
> > > app locally but the images are on a network somewhere, delay in
> display is
> > > inevitable. Try co-locating the images with where the app is executing
> by
> > > either putting the images on the workstation or run the app on the
> server.
> > >
> > >
> > >
> > > Also, if you're using high-quality jpegs, try a lower quality or
> > > resolution
> > > to reduce file size and therefore reduce the time it takes to
> > > load/display.
> > >
> > >
> > >
> > > Another possibility, and I have to say this is a stretch, would be to
> > > store
> > > each image in its own temporary table and use db images instead of
> > > variable
> > > images. That way, when the image changes, you update the table then
> issue
> > > a
> > > PROPERTY TABLE tablename 'REFRESH' to refresh just the one table and
> > > therefore just the one image.
> > >
> > >
> > >
> > > Emmitt Dove
> > >
> > > Manager, Converting Applications Development
> > >
> > > Evergreen Packaging, Inc.
> > >
> > > emmitt.d...@everpack.com
> > >
> > > (203) 214-5683 m
> > >
> > > (203) 643-8022 o
> > >
> > > (203) 643-8086 f
> > >
> > > emmitt.w.d...@comcast.net
> > >
> > >
> > >
> > >
> >
> >
>
>