on that topic there was a thread here that may be worth a read
http://www.talkgraphics.com/showthread.php?t=12856
on that topic there was a thread here that may be worth a read
http://www.talkgraphics.com/showthread.php?t=12856
-------------------------------
Nothing lasts forever...
Wow.. very nice, David. Thanks for taking the time to explain this to me. This was a big help. Yeah,.. it's not as "fast and easy" as the nifty bevel button, but the results are much cleaner using your method.
That makes a ton of sense, David. Thanks again for all your help!
All vector objects are ultimately rendered using bitmap techniques because the screen is a bitmap!
The bevel bitmaps are generated on the fly from the vectors data so unlike a bitmap program they are not fixed once you've drawn them and their resolution can be adjusted as needed.
Normally the bitmap resolution is calculated to be invisible at the current zoom factor but as you zoom in, increasing the effective resolution required to render the object, the bitmap becomes so big that it would take many many megabytes of memory and would be very slow to render. So Xtreme places an upper limit on the resolution of some bitmaps, bevels in particular, and above that limit you will start to see the pixels.
A similar thing is hapenning during printing or exporting to high-res file formats.
Phil
In my (albeit limited) experience, this is how CorelDraw also handles these things. Xara however does it much much faster (on the same hardware). And although CorelDraw uses the 'interactive' word for transparencies, shadows etc - it's nothing like Xaras 'Live & Real Time' interactivness.
Bottom line for me, I can't create in CorelDraw what I can with XaraXtreme.
Bookmarks