Thanks for the info Ryan, that should prove useful in the future.
-Steve
--
*Ryan Matsikas* wrote :
Some people on this list use mCom and a few of the developers (including
myself) are also on the list, if you aren't having luck with M
Could someone please email these .mxps to me so I can do a visual inspection?
;-)
Mike
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought t
I bought them and my experience is very similar. EXTREMELY
disappointed. The skinning is good but the lack of documentation and
support is appalling. The documentation has holes all throughout it.
I've never gotten a response from the support ticket system. Even
when I wrote asking for a re
Sorry to double post, but I replyed to Steve's (different Steve) thread with
the same title. Check it out.
On 6/7/06, Rich Rodecker <[EMAIL PROTECTED]> wrote:
yeah, theri sample app on the homepage has a note on the bottom that
says the app was built with eariler versions of the components, and
Steve,
Some people on this list use mCom and a few of the developers (including
myself) are also on the list, if you aren't having luck with Metaliq's
response's to your issues feel free to ask here. Also there is a google
group for mCom that a few users are on, and some of the issues/bugs have
yeah, theri sample app on the homepage has a note on the bottom that
says the app was built with eariler versions of the components, and
the set was being updated, but i didnt see anything on the site
regarding updates.
On 6/7/06, Steve Polk <[EMAIL PROTECTED]> wrote:
The components themselves
The components themselves are great. They are lightweight, generally easy to
skin, and the API is very compatible with the v2 components that MM ships.
With that said; the company that acquired the set, Metaliq, does not appear
to be interested in documenting or supporting them. I have sent numero
7 matches
Mail list logo
