On Nov 7, 2018, at 2:00 PM, Robert ListMail wrote:
> I’ve been working with button images which the picture library... While doing
> this I noticed one nice feature of the picture library. When dragging button
> graphics from the picture library to a form (assuming that the picture
> properties are defined as a split object), the destination object is assumed
> to be a picture button and is sized properly (48x48). When I do this with the
> resource folder as a source, I get just the graphic (not a button) and I have
> to muck with the sizing properties since this apparently cannot be set via
> the resource tab of the toolbox. Any suggestions about this subject? What’s
> the consensus about where to store these resources? I think 4D is suggesting
> resources (the external resource folder) is the future but clearly there are
> some picture folder benefits. What do you use?
Use what you like and what works best for you. That’s the real answer.
I love Picture Library and use it for many reasons. Faster, easier, less chance
of breakage when installing new versions and moving structures around.
Also no need to do “duplicate resources locally” of every picture in
“Resources” whether the user ever needs them or not. Picture Library works just
like forms and methods. You only get what you need when you need it, and only
if the locally cached version needs to be updated. That’s a big advantage to
me. Why copy a 50MB “Resources” folder of images when 4D Client starts up? The
client may never need 49MB of those images.
Picture Library is not going anywhere. There’s no talk of deprecation as far as
I know.
Tim
*
Tim Nevels
Innovative Solutions
785-749-3444
timnev...@mac.com
*
**
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**
