Recently I started storing all graphics used in a solution in one module. So far, a couple of issues with this strategy:
1/ if you import a solution that uses a “graphics module” under a new name, all objects that use a graphic from the graphics module no longer have the graphic attached. (Which can be a REAL pain to go through and reset.)
2/ if you import a solution (same name) to a new location that is exported without including the graphics module – again, graphics are detached. Even if the graphics module exists at the new location already. (Not such a big deal as you can work around it.)
Yea, not as useful for lots of interface images. Roll over images can’t be handled this way for starters. And you would need either a calculation or a relationship for each distinct image on a layout. That would get out of hand in a hurry for some of my layouts!
david:
Recently I started storing all graphics used in a solution in one module. So far, a couple of issues with this strategy:
1/ if you import a solution that uses a “graphics module” under a new name, all objects that use a graphic from the graphics module no longer have the graphic attached. (Which can be a REAL pain to go through and reset.)
2/ if you import a solution (same name) to a new location that is exported without including the graphics module – again, graphics are detached. Even if the graphics module exists at the new location already. (Not such a big deal as you can work around it.)
Are there any solutions for this bug yet? I have same issue with 3.0.2
What issues are you having? All of these and the “duplicating” graphics problem have been resolved in my limited testing. But I am not working heavily in v3 yet.