Yellow: I’m not sure why I should respond to you as it seems you already have an import path that works and which you like better but…
First regarding Python vs. hard coded - What difference does it make? This is one case where the ease of writing/reading Python trumps the small increase in speed possible with C.
Thanks for taking the time to respond.
First of all i recognise the importance of your script and as i’ve mentioned previously in this thread it’s very welcome, anything that makes blender better is very welcome and I’m sorry you feel you have to defend yourself.
Now my turn to defend myself, feel free not to read or respond. On reading your response to the import errors listed previously and that you stated the script was not coded for CVS version i interpreted that incorrectly, it would seem, that there would be ongoing problems with your scripts compatibility (and other scripts) with the Python API regarding back compatibility, so my thinking was as everyone who has been trying to import DXF’s for years by using work arounds, it just felt to me that the hardcoded was closer to successful imports than your script in it’s current state, if only a dev would look at the hardcoded & fix it, hence my opinion that maybe if someone looked at the hardcoded blah blah… but i understand now from what you’ve said that your script is/will be more flexible. My comment about 3D import related to the hardcoded comment not what or what not you should put in YOUR script. But other 3D formats do offer more / better features, i was unaware the very reason you were writing the script was for 3D solids import.
I was not saying that you shouldn’t bother with your script because MY workaround workflow works and your script doesn’t presently, that’s not my business. I was responding to LetterRips query as to the status of the script for inclusion with the upcoming release and as there was little other input on the thread as to whether the script worked i posted the error messages i was getting. Which leads me to my second defence:
LetterRip:
kitsu,
please ignore detractors - there are unfortunately many users who are of the opinion ‘if it isn’t useful to me - why bother’. I personally think it is great that you intend to add 3D support and feel it will be of great benefit
I posted error messages in response to your status requests, LetterRip, at a time no one else was, I took the time to, because i’d really like to see Kitsu’s script work for everyones benefit, the 3D mention as i explained related to the hardcoded, to be honest i didn’t know what purpose Kitsu was writing it for, it appears more for 3D purposes.
As for Accutrans/ACAD R12/every other odd dxf file - a good importer should be able to handle them all as long as they are well formed. The way the dxf format is put together leaves very few options for creating non-standard files.
All the files i tested were standard AutoCAD R12 files and they failed with your script, whatever accutrans does, which doesn’t appear much going on filesize changes it makes them compatible with Blenders internal DXF import.
I don’t know why I should have to defend myself here. I am making this thing for me and sharing it with you. If you don’t want it, don’t like it, think you could do better, go away! You are just wasting my and everyone else time spouting off about non-sense. If you have meaningful bug reports, weird dxf files, feature request, etc. thats fine, But I’m realy not interested in hearing anything else about “…forget it, quicker and easier just to open in openoffice, export as SVG and import into blender…or use accutrans to convert to a DXF that the old hardcoded DXF import handles…”.
I hope my explanation mitigates some of what you’ve said above, i don’t think posting error messages is wasting anyones time especially when status was asked, the hardcoded import fix mention…blah blah may be nonsense to you not me, the DXF files i’m testing come straight out of AutoCAD there’s nothing ‘weird’ about them, and mentioning the workaround was for others benefit and on this thread for the purpose of history, for future visitors searching DXF import issues on BA, until your scipt works, it’s not nonsense the work around works, i also credit in earlier posts Ne0n and JMS for their valuable work and input on the SVG/Open Office work around.
There, perhaps i wasted even more of peoples valuable time, if anyone has read this through.
Although i think i’ve already thanked you Kitsu for you work i’d like to thank you again. I look forward to using your script when it works.
The files i tried last night at home all failed except one, a 1.7mb file of simple lines, on one layer. Yes i had noticed the ‘wait cursor’ switching off and a minute or two later either an outright crash wiping the blender session off my desktop (linux) or freezing solid on windows, or just the once a successful import, which was good to see.
