Re: Civakatirswami's color resource suggestion
Imagine how great it would be if it were in English JR John Ranck Harvard University Development Office 124 Mt. Auburn St. Cambridge, MA 02138 [EMAIL PROTECTED] http://www.simmons.edu/~ranck Archives: http://www.mail-archive.com/metacard%40lists.best.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to [EMAIL PROTECTED], not this list.
Images in memory
I've got a stack that repeatedly sets the filename property of various images. Is there a way to keep these in memory even after the image content changes so that, once loaded in, they are immediately available? Sort of a pre-buffer-and-store thing? I know I could store the images in the stack and set a button icon to use them instead, but there are almost a megabyte of images and the stack would get fairly bloated. -- Jacqueline Landman Gay| [EMAIL PROTECTED] HyperActive Software | [EMAIL PROTECTED] Custom hypermedia solutions | http://www.hyperactivesw.com 612.724.1596 | 612.724.1562 - fax Archives: http://www.mail-archive.com/metacard%40lists.best.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to [EMAIL PROTECTED], not this list.
Re: Images in memory
At 5:14 PM -0500 6/13/00, Jacqueline Landman Gay wrote: I've got a stack that repeatedly sets the filename property of various images. Is there a way to keep these in memory even after the image content changes so that, once loaded in, they are immediately available? Sort of a pre-buffer-and-store thing? I know I could store the images in the stack and set a button icon to use them instead, but there are almost a megabyte of images and the stack would get fairly bloated. You can store image data in custom properties, so I guess you could could roll-your-own buffer of sorts, for example storing the five most recent images in custom properties. This is just a first thought .. I'll leave you to work out the implementation details. :) But a megabyte of image data doesn't seem too much these days (unless the stack is already on the large size). An alternative to the button approach is to put all the images into custom properties, and have a single placeholder image. Then just "put" the custom properties into the image object to display. I don't know the pros and cons of the two approaches, but using a button to display an image has alway struck me as odd. Nice to have the choice though. Cheers Dave Cragg _ The LACS Centre (Business English Training Resources) mailto:[EMAIL PROTECTED] http://www.lacscentre.co.uk _ Archives: http://www.mail-archive.com/metacard%40lists.best.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to [EMAIL PROTECTED], not this list.
File selector-MacOS
the problem with this (new) Navigation Services file selector on MacOS is that you can't select a folder like with the old one unless I'm missing something. Besides it has no live scrolling and really looks and acts like a visualBasic thing. I'd suggest defaulting to the old file/folder selector. Regards, Andu Archives: http://www.mail-archive.com/metacard%40lists.best.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to [EMAIL PROTECTED], not this list.
Re: Subject: Images in memory
On 6/13/2000 11:05 PM Jacqueline Landman Gay [EMAIL PROTECTED] wrote: I've got a stack that repeatedly sets the filename property of various images. Is there a way to keep these in memory even after the image content changes so that, once loaded in, they are immediately available? Sort of a pre-buffer-and-store thing? I know I could store the images in the stack and set a button icon to use them instead, but there are almost a megabyte of images and the stack would get fairly bloated. Jacque, I'd suggest storing the filenames into a custom property. This would be instantly accessible. Something like "set the filename of image "myImage" to line k of the storedfilenames of image "myImage" Is this what you are looking for? Raymond -- Jacqueline Landman Gay| [EMAIL PROTECTED] HyperActive Software | [EMAIL PROTECTED] Custom hypermedia solutions | http://www.hyperactivesw.com 612.724.1596 | 612.724.1562 - fax Archives: http://www.mail-archive.com/metacard%40lists.best.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to [EMAIL PROTECTED], not this list.
Re: Subject: Images in memory
Not exactly. Getting the filename isn't a problem; I'm trying to avoid the hit that happens when you load an image from disk. I spent the evening putting the images into the stack and changing everything to use buttons with icons. It seems snappier. But if there is a way to "preload" images and have them stay in RAM, I'd like to know for future reference. "You know, there's an easier way to do that..." Create an empty image (x). put url "binfile:path to file" into temp (on openStack or something) put temp into image x -- Jacqueline Landman Gay Regards, Andu Archives: http://www.mail-archive.com/metacard%40lists.best.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to [EMAIL PROTECTED], not this list.
Re: Subject: Images in memory
Recently, Jacqueline Landman Gay at [EMAIL PROTECTED] wrote: if there is a way to "preload" images and have them stay in RAM, I'd like to know for future reference. You can load them offscreen. One technique you might use is to reference images locally within your stack via a button object. Set the filename/s of your offscreen image/s. Then use a button as your onscreen "image" and set its ID to that of the offscreen image/s. Regards, Scott __ Scott RossiTactile Media - Multimedia Design Creative Director Email: [EMAIL PROTECTED] Web: www.tactilemedia.com Archives: http://www.mail-archive.com/metacard%40lists.best.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to [EMAIL PROTECTED], not this list.
Re: Subject: Images in memory
Jacqueline Landman Gay wrote: "Raymond E. Griffith" wrote: On 6/13/2000 11:05 PM Jacqueline Landman Gay [EMAIL PROTECTED] wrote: I've got a stack that repeatedly sets the filename property of various images. Is there a way to keep these in memory even after the image content changes so that, once loaded in, they are immediately available? Sort of a pre-buffer-and-store thing? Jacque, I'd suggest storing the filenames into a custom property. This would be instantly accessible. Something like "set the filename of image "myImage" to line k of the storedfilenames of image "myImage" Is this what you are looking for? Not exactly. Getting the filename isn't a problem; I'm trying to avoid the hit that happens when you load an image from disk. I spent the evening putting the images into the stack and changing everything to use buttons with icons. It seems snappier. But if there is a way to "preload" images and have them stay in RAM, I'd like to know for future reference. If the images are stored in a stack, you can cause the stack to load without opening it by "touching" it (referring to it) from a script somewhere. As long as memory isn't needed for something else, it'll be there. For example, the script of stack "start" could contain this: on openStack get the nothing of stack "images" end openStack This assumes that stack "images" does NOT have a custom property named "nothing". Phil -- Jacqueline Landman Gay| [EMAIL PROTECTED] HyperActive Software | [EMAIL PROTECTED] Custom hypermedia solutions | http://www.hyperactivesw.com 612.724.1596 | 612.724.1562 - fax Archives: http://www.mail-archive.com/metacard%40lists.best.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to [EMAIL PROTECTED], not this list. -- Phil Davis [EMAIL PROTECTED] (503) 557-5656 Archives: http://www.mail-archive.com/metacard%40lists.best.com/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to [EMAIL PROTECTED], not this list.
