It just does not affect you, it affects many people that dont know
they are affected.
I believe, after talking to RS, that they feel that imbedded
libraries are better then yet another DLL to add to your app as is in
the case of quesa libraries.
I personally dont think this is true and hence the, help me say it
"ILL" effect that quesa has right now where it does not allow for
certain Declares to be done due to the current linking issue.
Come on, there should be more then 11 people affected.
How hard is it to change this from the side of RS?
Kind regards,
Giovanni
rbml at alphaview dot com
On Aug 31, 2007, at 6:48 PM, Thomas Moore wrote:
> Joe, I have now signed on. Is there another good way to tell RS how
> this affects me personally?
>
> In the meantime, my main reason for using declares is that I can
> easily create simple geometric objects in Quesa (cylinders, cones,
> rectangular boxes, and spheres) that look very good and (most
> importantly) whose dimensions can be very easily and
> straightforwardly set in code. I know that I can create 3DMF string
> objects and manipulate the string in code, but I tried and tried with
> this and gave up in despair -- it was *much* easier (for me) to do
> this with declares! Also, I could never get spheres to look right --
> they looked unacceptably lumpy, whereas the Quesa spheres really look
> like perfectly round spheres. It was also very important to be able
> to draw these things *fast*, and I worried that creating a tri-mesh
> sphere (or cylinder or cone) with sufficiently small triangles so
> that that it looked good would take a long time to draw (when I might
> have to draw several hundred of them in a fraction of a second).
>
> Can anyone suggest a straightforward way other than declares that I
> can use to draw such objects and set their dimensions in code?
>
> Thanks for any ideas, Tom
>
> I would be happy to rewrite my program in pure RB code if I knew how
> to overcome
> On Aug 30, 2007, at 8:04 AM, joe at strout dot net wrote:
>
>> On Aug 30, 2007, at 14:47 UTC, Thomas Moore wrote:
>>
>>> So what I am extracting from all this is that there is no Windows
>>> solution other than
>>>
>>> (1) rewriting the code entirely to avoid declares (difficult at
>>> best,
>>> maybe impossible)
>>> (2) rewriting the code entirely to avoid RB3D APIs (also very
>>> difficult at best)
>>> (3) getting RS to change RB allow declares to the internal
>>> library in
>>> Windows builds (also difficult)
>>>
>>> Sounds like I am in a bad place with this project. :-(
>>
>> Yes, I too have a number of projects which now can't be ported to
>> Windows due to this change in 2007r3. Please sign on to:
>>
>> <http://www.realsoftware.com/feedback/dhqxojbs>
>>
>> and use any opportunity you have to make it clear to RS how important
>> this is to you. Failing any action on their part, you can go back to
>> 2007r2 to make your Windows builds, but of course you then miss
>> out on
>> any bug fixes or new features added since then.
>>
>> I'm sure this change was intended to make Rb3D easier to use on
>> Windows, but I think it's had the opposite effect. I really hope
>> they'll do something about it soon.
>>
>>
>> --
>> Joe Strout -- joe at strout dot net
>
> -------------------------------------------------------------
> This message has been scanned by Postini anti-virus software.
>
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
>
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|