 | | Re: L3P v1.3 for Mac OSX
|
|
Lars, I used L3P this weekend. Since this is my first time using it, I tested only very simple uses. No problems found, unless you consider it a bug that it behaves badly with CR line endings. It's hard to tell which input file it is complaining (...) (22 years ago, 4-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) Erik, How did you render the POV files produced by l3p. Neither POV-Ray 3.1 (Classic) nor POV-Ray 3.5 (OS X) liked the file that l3p produced. When I dropped the file onto the applications incons in the Dock, the applications just ignored the (...) (22 years ago, 5-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) How does it behave badly? Does it fail to read some lines? L3P uses fgets and then removes trailing \n and \r, but perhaps this fails on "old" mac files, which I believe use the CR ending. On MacOSX, \n is mapped to LF, so how do you read CR (...) (22 years ago, 5-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) Sure, if you tell me what exactly what you want... /Lars (22 years ago, 5-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) Well, I don't really know. As I said, James said to do this at the command line /Developer/Tools/SetFile -c "POV3" -t "TEXT" /Users/yourname/yourfile.pov and after doing that, the POV-Ray programs processed the files normally. I don't know why (...) (22 years ago, 5-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) I wonder if this could be solved with something as simple as doing an fopen() with "wt" instead of just "w"? And... And... I just can't help myself here, sorry Lars... If the code were available you might get better, more helpful or accurate (...) (22 years ago, 5-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) Essentially the \r make it one big line. L3P says it has the wrong number of fields. Maybe it reads the buffer limit and tries again because there is a variety of error messages per file. Now that you ask I don't know how one can use fgets for (...) (22 years ago, 5-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
This is more of an issue with POV-Ray. It has everything to do with Macintosh Meta data. l3p creates files with no meta data. If you type: /Developer/Tools/GetFileInfo -c /path/to/.pov /Developer/Tools/GetFileInfo -t /path/to/.pov You get: "" Which (...) (22 years ago, 5-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) Interesting idea. Unfortunately either way fopen creates a file with no Mac type or creator code at all. Because I told the Finder once to open a .pov file with BBEdit, it knows to do that for me. But I still get a blank icon because it has no (...) (22 years ago, 5-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) I think ldglite has this same problem. Remember when we had the discussion about using the linux parts vs. the parts that Erik has for download? I could not get Erik's parts to work with l3p either. (...) You can mix Cocoa and Carbon, can't (...) (22 years ago, 5-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) These might not be the cleanest solution. I want the same binary to launch on OS 8.6 or 9. But I think you can still try to bring in a Cocoa framework at runtime to a CFM process though. CFM is required on OS 9. Mixing Cocoa and Carbon is (...) (22 years ago, 6-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) I found the sample code that loads the System.framework from a CFM carbon app and runs a unix process with popen... (URL) (22 years ago, 6-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) I suspected that POV-Ray was just being difficult, especially when simply adding (I didn't know if it was adding or changing the file type) the text file type. (...) Actually, that makes sense. But do you think that they are doing the "text (...) (22 years ago, 6-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) I agree. It seems like a step backwards. (...) Ahh.... so it is a 10.2 thing. Thanks, Chris (22 years ago, 6-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) I wondered that too. I would think that it wouldn't matter. If it tried to open a binary file, I don't think it would be any worse than openning a SimpleText or some other "TEXT" file. POV-Ray still has to check the file for proper POV-Ray (...) (22 years ago, 6-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) If, IF I get it working. I have no idea what I am doing most of the time, but sometimes get it to work anyway. With OS 9 I could create a drag-and-drop capable scriptlet/applet, but with OS X I cannot figure it out :( (...) It seems that there (...) (22 years ago, 7-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) Don't worry, neither do I. ;-) (...) The OS 9 script should compile and work on OS X too. I haven't been paying attention to AppleScript changes for OS X since May, but back then the scripts pretty much did the same thing they did in OS 9. (...) (22 years ago, 7-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) I do consider it an error. I have now made an L3fgets that can handle any line ending. I have uploaded an update (URL) try it on the original problem files. /Lars PS. Here is L3fgets, You can use it in ldglite if you like. As Paul DiLascia (...) (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) If it is possible for you to identify the problem files, could you let me know the names of the bad files. Steve and I try to make sure that everything in the official library has DOS-style line endings. If there are official parts with (...) (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) Hey, thanks Lars. Where should I put it? L3Input.cpp, or a separate file like platform.c? Don (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) I have put it in L3Input.cpp because I only used fgets there, but if you can benefit from L3fgets() elsewhere you can put it in L3fgets.c or in platform.c as you wish... /Lars (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) I guess what I was trying to say (without actually saying it) was "Can I have the latest version of L3Input.cpp?" Don (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) Chris, There are no Mac "official" parts. LDMC ((URL) points people to download the linux parts: www.ldraw.org/refere...ary.tar.gz The parts with mac-style endings are coming from Erik Olson's parts which one downloads when they download (...) (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
Yes, the CR endings are my fault. When you download the LDRAW.sit file from my website you're getting a copy of what I have on my working disk. I've fixed mine since trying L3P but haven't uploaded it. I think I will just point to the Linux (...) (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) Umm, fgets already does what 2) says above (unless you mean when end of file is reached and the function returns NULL). I'm not actually sure what goes into the string when fgets returns NULL. If no line ending is found (either due to EOF (...) (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) Thanks. I thought we had that under control - just wanted to be sure. Chris (22 years ago, 11-Dec-02, to lugnet.cad.dev.mac)
|
| |
| | Re: L3P v1.3 for Mac OSX
|
|
(...) Right! I must have been sleeping or thinking of strncpy...? Please delete 2) from the comment. (...) According to the CRT source ungetc doesn't use fseek, but with L3fgets the need to open in text mode has gone, so I might as well open in (...) (22 years ago, 12-Dec-02, to lugnet.cad.dev.mac)
|
