Any way to see dimensions of a texture from an MXP file?

Question

Hello all,
Running into a snag I hope someone can help me with. I'm using some textures that are in an MXP package for some recent designs. Now that the designs have reached the approval stage I need to send them off to the developer for slicing and coding of the actual site. The issue I'm having is that since the textures are part of an MXP extension, I need to get the exact dimensions to the pattern so I can tell the developer where to slice the background but can't find any way to get this information.
I know under normal circumstances you can go to your textures folder and just look at the dimensions in a file browser. Because this is an MXP file though the textures aren't installed into any directory (that I'm aware of or can find) and so I can't find a way to look at the texture file outside of Fireworks to determine dimensions. I even tried downloading a decent extension tool that might have hepled, but it only looks at textures in the texture directory, not unpacked MXP files.
Can anyone tell me how to get this information, or if there is a way to look into the MXP file and get the dimensions I need etc? I hate having to create an object and guess at getting the proper dimensions by trial and error all the time. One of these patterns in particular would be really hard to determine with that method because of how it's made. Any information would be greatly appreciated... maybe I'm just missing something obvious? The texture palette in native to Fireworks doesn't have any fnuctionality other than a crude list that I can tell. It's hard to believe that after all this time that software developed for use on the web wouldn't allow viewing of exact dimensions for a repeatable effect. I mean at some point it's a given it will have to be sliced for the web right?
Thanks in advance for any information!

Answer 1

Thanks for the additional insight. I'll try to dig deeper with a Google search and see if I have any luck. I got the initial idea to check the "users" path in Windows from a Google search but didn't see any other suggestions of where it would be located other than in that directory. I poked around all the other user directories but none of them contained Adobe paths in them. It's very difficult to find information about Fireworks textures (and often Fireowks in general) in a search though because you mostly get info about how to install textures or people posting their textures for download. I guess the large quantity of those "free packs" tends to push more informative posts down the search rankings? Also the lack of use as compared to Photoshop etc. seems to mean there is a lot less tutorial and help information in general available. Much of what is out there I have noticed is for very old versions. I'll look around some more and see if I can find any more path suggestions.
The patterns DO show up in the textures option under the standard color/stroke/texture panel and that is where I have been selecting them. I have a small library of 3rd party textures that I attach as an additional directory for textures and patterns, but haven't gotten around to that yet since I installed CS6 and because many of the textures I use more commonaly are in MXP style packages rather than loose files. I have also verified that the textures in question are not in the 3rd party folder. The fact they show up in the internal texture selector gives me hope that they can be found though. One concern I have is that they are being stored somewhere very difficult to find and the texture in question is being called something on the actual file name that is different from the name given in the Fireworks texture pallete. If I could find a valid folder I could visually identify it regardless of name, but finding that magic folder is the issue right now lol!
I wasn't sure how MXP packs worked, It kind of seems like this particular MXP is behaving like you explained styles to work. I admit to knowing very little about how MXP files are put together but I'm starting to wonder if there are options to establish whether you want your content accessible or not, you know for licensing protection etc. Many people are OK with letting others use their patterns, but do not want anyone editing or redistributing them. If the MXP format allows you to restrict access to those patterns it may be why I see so many of the textures starting to be presented this way, other than ease of installing for the average user. In fact most of the add-ons I've gotten for all Adobe software in the past year have almost all been through extension installs, be they free or paid materials.
In the meantime do you know of any add-ons that simply add some file information to the texture panel? All I need is for it show the dimensions along with the little preview that pops up when you mouse over a name. I'm amazed that they have never got around to doing this. It seems like it would be terribly simple to implement on Adobe's side and it would be extremely useful for most users I would think. I have seen many people in the comments of various forums etc. as I have searched for an answer that were asking for this kind of feature so there is definitely a need for it. I don't use these particular textures enough to bother the creator with special situations... I can find the dimensions manually with some trial and error by creating an object in Fireworks and playing around until I hit the sweet spot. I would just like to have a fast accessible option so that I don't have to keep a written log somewhere of all my extension installed textures and their dimensions, or have to stop and pick out the dimensions every time i use a new texture. It's not so bad when you're doing it all no your own, if it's off you can adjust on the fly as you code. In a development team environment it can cause some issues having to go back and forth with someone else until you get it just right. I know the coders here don't like to fool with "graphic issues" at all haha!
Once again thanks for the tips. If you (or anyone else) have any more ideas I would love to hear them. I'll poke around some more and If I manage to find a work around or solution I will post the result for the benefit of the community.