Re: SW2006 file format



Well, now that I am in the conversation... I am positive it is not for lack
of trying on the part of SW to get it right with one file format as a
significant portion of my time each year with Beta testing is spent dealing
with conversion problems and submitting conversion errors even before I get
to see what's new and submit enhancment requests. I am sure they would
forego this every year if they could - I know I would. However, each year
it gets better with less and less conversion errors. Although it is up to us
to help them by continueing to stay active and give positive criticism,
these changes are for the better. You may have a preference for some other
CAD program and are therefore biased - as am I for SolidWorks - but I have
made the decision to use it for the long haul and thus stay active in its
development; as do many other people including the several thousand beta
testers each year.


"abc" <abc@xxxxxxxxxxxxxxx> wrote in message
news:BNGdnT6_pfC1Z7zeRVn-iw@xxxxxxxxxxxxxx
> Dude
>
> I hate to say this but I think your the idiot. To blindly assume and
> accept that no version compatibility of any sort is possible within SW is
> totally BS and you've totally suckered yourself into believing what they
> want you to believe.
>
> I agree that some feature types cannot import/export due to new feature
> enhancements. So what? Let them still import as dumb solids anyway and
> let the rest of the features import as normal. At the very least, let
> drawings import.
>
> Take a look at all the things FeaturWorks can do now. It can even
> recognize features to use as hole wizard features in dumb solids. Hard to
> believe that these kinds of technologies can't be used within SW on their
> own file structure for translations.
>
> Look at the evidence. You can export files as ProE, and Catia, but you
> can't export older versions of SW. You can import Catia, Pro E, UG,
> Inventor Solidedge, and Cadkey. But you can't import newer SW files.
> They got it rapped up tight only for themselves.
>
> As service packs are released for older versions of SW, they could include
> updates that would allow for translations to open newer file versions of
> SW. When a version of SW is no longer supported, then they could stop
> worrying about translations for it.
>
> I know it could be done, but they have no financial incentive to do it and
> they want everybody think it's not possible.
>
>
>
> <ken.maren@xxxxxxxxx> wrote in message
> news:1126290532.544045.174540@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>i hate to do this but you're an idiot. you are talking about a 3D file
>> vs. a flat 2D file. That's nearly no different than word files being
>> opened from office 97 to office 2003 and back and forth. There's
>> nothing to translate.
>>
>> Tell me how that one might translate a SolidWorks file that uses the
>> flex feature back to SolidWorks 2003? There have been many theories
>> and good ideas too but you post is by far the most idiotic post I have
>> read in a long time.
>>
>> KM
>>
>
>


.



Relevant Pages

  • Re: Switching between color spaces
    ... Chinese is also a very simple language, and it has worked for millennia. ... Who is doing that conversion? ... PostScript when printing to a PostScript printer and use the PS printer ... driver's "pass through" feature. ...
    (comp.lang.postscript)
  • Re: Configuring the VB 6 to VB 2005 Converter (WAS: Re: VB 6 developers and .Net)
    ... Mike Ober. ... How do I turn this "feature" off? ... I was just wondering how widespread or otherwise is the conversion ... If the conversion is not that widespread what is the reason. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Writing bulletproof code
    ... Those conversion operators are a hand-made ... Even if fubble is defined as ... Range-restricted types may be a famous feature of Ada, ... particular relevance to any discussion of C++, a language which does not ...
    (comp.programming)
  • Re: SW2006 file format
    ... You're first statement was vague and just down right dumb. ... > I agree that some feature types cannot import/export due to new feature ... > updates that would allow for translations to open newer file versions of SW. ... >> and good ideas too but you post is by far the most idiotic post I have ...
    (comp.cad.solidworks)
  • Re: PackageKit run scheduling?
    ... if/when all the translations are done or if a new feature in the 0.4.x ... My only slight worry is the fact that the codec ...
    (Fedora)