Loading images for use with LC6.5 and resolution independance

[Monte Goulding]

On 15/11/2013, at 2:45 PM, Scott Rossi wrote:

> On 11/14/13 6:16 PM, "Monte Goulding" <monte at sweattechnologies.com> wrote:
> 
> 
>> There's probably no reason why you couldn't continue to import images
>> and swap them manually as button icons.
> 
> Of course, but then what's the point of the engine having a naming
> convention and auto-scaling features?
> 
They are still scaled.

> 
>> It does mean a little bit of thought probably needs to go into a new
>> custom control scheme...  I'll raise on the engine list that relative
>> paths for images should be looked for relative to the stackfile a
>> behavior is on if they aren't found relative to the stackfile the image
>> is on.
> 
> IMO, the engine's image-locating process should be consistent: look within
> the immediate the stack, substacks, loaded stacks, and extend the search
> to external files if needed or specified.

I'm talking about relative file paths for filename not icons. They currently try and resolve against the filename of the stack then against the default folder. They should iterate through the filenames of the behavior heirarchy before trying the default folder.

Cheers

--
M E R Goulding 
Software development services
Bespoke application development for vertical markets

mergExt - There's an external for that!