I am fairly new to HOOPS, so sorry if the question is dumb.
I am trying to export my scene as a 2D pdf. It does not work, because /driver/pdf segment does not exist. According to documentation, PDF is supported on all platforms (so far I am testing on Windows 7, 64bit), however I only see these driver segments existing:
/driver/2ddriver
/driver/3ddriver
/driver/image
/driver/msw
/driver/null
/driver/opengl
/driver/opengl2
i.e. a number of drivers that are supposed to be supported on all platforms do not exist, e.g. postscript, printf etc.
I presume something is wrong with my HOOPS installation, but what?
Thanks!!!
Found it! :)
My /bin/ was missing pdf2120_x64.hdi - once I added it, driver got magically created and pdf export worked.
The .hdi file is actually a renamed .dll and can be viewed in dependency walker.
Related
it might very well be that this question is ill-posed.
What I try to do is compile a code from GitHub here https://github.com/stereolabs/zed-oculus
to get the ZED stereo camera video displayed inside the Oculus.
I am working with Visual Studio for this project and unfortunately I am a total newbie with CMake. I came across several tutorials how to work with CMake and while I understand how to add include directories for a VS solution (without using CMake) I completely do not understand what these 2 beginning parts of CMake-code are trying to do:
SET(OCULUS_PATH "OCULUS_SDK_ROOT_DIR-NOTFOUND" REQUIRED CACHE STRING "Path of OVR SDK folder. eg: C:\\ovr_sdk_win_0.17.0\\OculusSDK")
SET(SDL_PATH "SDL2_ROOT_DIR-NOTFOUND" REQUIRED CACHE STRING "Path of SDL2 folder. eg: C:\\SDL2-2.0.
I don't know even the correct syntax to use for the folders. On my system I have the Oculus SDK under C:\OculusSDK and the SDL under C:\SDL. Unfortunately all the examples I've found on StackOverflow so far look completely different or are using Linux based folder script.
So could please someone explain to me what the above rows of code are trying to accomplish and what code should I use given the names of my directories?
Thanks a lot!
the problem is obvious from the title, http://typeface.neocracy.org offline. It was used to convert fonts and used in conjunction with THREE.TextGeometry. But if it is offline, how is now possible to use custom fonts in three.js?
I made a new converter that outputs the same files as typeface.js.
http://gero3.github.io/facetype.js/
I loaded the source, but as far as I can see there is no chance to create the JS-font-files with this distribution. Maybe for someone with deep perl-knowledge...? In any case I installed perl, the ppm and dmake but trying to exec the Makefile only leads to errormessages about missing files. No - this is no alternative to the online-converter. Even worser: I didn't find any other converter or another side using the same one (cufon seems to create another format). So let's hope the site comes back to live - otherwise the great textfeature of three.js is worth nothing in the moment.
Ghostscript 9.0 doesn't support validation of the digital signatures in PDF document when doing PDF to image conversion. Instead, there's a question mark on the digital signature, and Ghostscript reports "Sig is not yet implemented". I'm thinking to modify the source code to get rid of the question mark, but I don't have any ideas to where I should modify in thesource code. Could any one give the hints for that? Any response will be appreciated highly, thanks.
Have you already tested the very latest release (which is v9.02)? If so, have you also tested the current 'HEAD' revision of their source code?
If your problem persists with these versions, the preparatory thing to start with is to download the (current, which is v9.02) Ghostscript source code from here or even check it out from their Git repository.
What you are trying to do can only be located in one of the following two modules of the Ghostscript source code:
the (PDF) interpreter
the (image) output devices
So I would first recursively grep the sources for "not yet implemented" or similar expressions, taking into account that there may even be line breaks within the string. (***I doubt the quote you gave in your initial version of the question is accurate, because it contained at least one typo.)
If I didn't find anything in the first step, I'd get into touch with the Ghostscript developers themselves. They usually hang around in IRC on Freenode, channel #ghostscript. In general they are a very friendly and helpful bunch, and they'll surely be able to give you some hints about how to solve your problem if you know how to ask...
I am new to Mac OS X programming and so I am going through an introductory text that includes building interfaces using Interface Builder (3.2.3) for both Cocoa and Carbon. Unfortunately I am having problems getting some of the examples I type in to run error free in the Cocoa and Carbon simulators. So I tried downloading the source code files from the publisher's website and found that they ran with no problems.
I'm trying to find the differences between the publisher's working and my non-working versions of the code. I started by just trying to compare the attribute settings as listed in Inspector but I could not find any differences. I then came across File Merge which I used to compare the .nib files for the two different versions. File Merge does show the differences but since I am unfamiliar with the markup language used in the .nib file and it lists too many differences to track down without being knowledgeable enough to know what is relevant or not, it really hasn't been very helpful.
My question is whether or not there is a tool or method available that will better show me the differences in the two versions of the code than what I can see in the Inspector window but also shows it in a more condensed and user friendly form than what is provided by File Merge. What is the recommended tool/methodology to debugging code in Interface Builder?
Also, can anyone recommend documentation where I can become familiar with reading and debugging the code in the .nib file in case that is the only way to find the differences?
Thanks
Check out nib2objc
Convert both yours and the example nibs to code.
It will convert nib files to what looks more like Obj-C code. Then just diff sections of them and see what's different. Should be pretty easy to read code vs NIB files.
The command line program ibtool can convert a nib into a text format, but I don't know if that will be sufficiently readable.
I am converting some docs to pdf using wkhtmltopdf (currently using perl and the command line versions). Is it possible to change the "PDF Producer", "PDF Version" and "Fast Web View" fields? The current defaults are "wkhtmltopdf", "1.4 (Acrobat 5.x)", and "No", respectively. I didn't see anything in the wiki page
Pass the following with the command line to see supported features: " --extended-help"
Not sure if those specific params are supported or not.
I patched wkhtmltopdf to support an additional flag recently, and it would be quite easy to add parameters to change those. I don't believe they are supported currently, though.
PDF Producer: Nope. Most apps want folks to know that particular app generated the PDF.
PDF Version: Nope, but trivial. The version number at the beginning of the file is just a courtesy really. What exactly are you after with this? Chances are you don't really need it. The PDF generated isn't going to acquire any features automagically just because the PDF claims to be this version or that. It's only really used so a viewer opening a newer PDF can say something like "I don't support this version, some stuff might not work". Because everything will work regardless (unless someone happens to have a VERY old version of Acrobat/Reader), I don't see the issue.
Fast Web View: Nope, and decidedly non-trivial. "Fast Web View" means everything needed to display the first page of the PDF is sorted to the front of the file, and there are various "hints" on where an app downloading the PDF can find this or that. It's not just a flag, not by a long stretch.
Zero for three. Sorry.