Subject:
|
Re: renderer.dll
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Sat, 22 Dec 2007 11:33:28 GMT
|
Viewed:
|
2783 times
|
| |
|
|
Travis Cobbs wrote:
> There's actually another alternative, and that would be to use
> LDView.exe itself. There's been code in LDView for a long time that
> is designed to allow an LDView renderer to show up as a child window
> of another program.
> The idea is that you would run LDView and use -float <window handle>
> on the command line, and it would then show up as a child window of
> the window handle you give.
Windows isn't really made for parenting other processes into another window.
Many things seem to work, but sooner or later you stumble over something
that doesn't, and there's no workaround. Also, it is not at all obvious that
all the users of a render DLL want to show the image in a window - it might
be used for further processing, sending to the web etc.
But it doesn't have to be a DLL, a separate process and some way of
communication is enough. AFAIK, LDView can render to a file, right? Does it
have a command line argument to run 'silent', ie not show up at all? If so,
everything is already ready.
Of course, if you want to host a 'live' window, the file method becomes too
slow - what about a shared memory mapped file (I don't really know the
performance of that)?
And finally, the DLL variant (which I have asked about before, too) - let's
decide a record structure which is the parameter block (size information,
render arguments, pointer to the area that should be filled with a bitmap (?
or DIB, or raw pixel data?), some extra fields for future expansions). Then,
when the interface is fixed, it just a matter for someone to create the DLL
:-)
--
Anders Isaksson, Sweden
BlockCAD: http://web.telia.com/~u16122508/proglego.htm
Gallery: http://web.telia.com/~u16122508/gallery/index.htm
|
|
Message has 1 Reply:
 | | Re: renderer.dll
|
| (...) Why should it be so complicate. I think about a DLL that gets only some informations like: Filename(to render),LDrawPath, LDConfigPath, BackgroundColor, DefaultColor and hDC for output. All other stuff should be done in a black box. This would (...) (17 years ago, 22-Dec-07, to lugnet.cad)
|
Message is in Reply To:
| | Re: renderer.dll
|
| (...) There's actually another alternative, and that would be to use LDView.exe itself. There's been code in LDView for a long time that is designed to allow an LDView renderer to show up as a child window of another program. It was never completed, (...) (17 years ago, 22-Dec-07, to lugnet.cad)
|
7 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
