Jump to content

mac-made mod technical problem


Recommended Posts

I'm having a problem with a menu mod (shown in the left and middle panels of the jpeg as they are meant to appear, except of course for the blurriness which is a result of compression), I made on my mac G4 running macos 9.1 and using macromedia's fireworks 4. The problem, as illustrated in the right panel of the jpeg, is that the masking of the color pink doesn't seem to carry over properly to PCs. Further, as illustrated for the 'pause' command in the right panel of the jpeg, when a bmp made using GraphicsConvertor is substitued for the version made using fireworks, PCs seem to ignore it and instead access the originals directly from the CM disk. Interestingly, my mac behaved in much the same way after I installed a modded version of 32000.bmp (from DeanCo's gunmetal interface mod) meant to change text color and font. Any offerings of insight into this would be appreciated. Thanks

trimmed_menus.jpg

Link to comment
Share on other sites

I should have been clearer on this. My point was that if there are practical work-arounds they may involve more than just coordinating masking colors between mac and pc. The mask was defined by me to be, and therefore displays on my mac as, the standard shade (255,255,0) of pink. I then converted the files from the png format in which I built them to the standard bmp format required for public consumption in which in particular the masking color remains unchanged at (255,255,0). After running these bmps through my macmod convertor app as usual they appear without problems on my mac as illustrated in the left and middle panels of the jpeg appearing in my initial post. The problem is that despite the fact that the masking shade (255,255,0) of pink shows up apparently unchanged on pc's, the masking effect is nevertheless destroyed. It is therefore not clear to me how the claim that pc's can "see all the colors that a mac can and more" would bear on this problem. So why doesn't the mask carry over to pcs properly? I suppose it is possible that the problem may be the result of some relatively benign and thus easily correctible incompatibility between color tables as they are arranged in macs vs pc's and their applications. But based on the foregoing, I'm skeptical of this. Also, it is not clear to me how such a solution would explain in any obvious way the anomalous "ignoring" behaviour described at the end of my initial post, though this may be unrelated to the problem at hand. A point made by DeanCo (who has also been spending time thinking about this) more or less consistent with this point of view is that the windows version of CM is a port of the macintosh code in which CM was originally written.

Link to comment
Share on other sites

×
×
  • Create New...