I have Ult. Home on one and Prem on another both handle Clipview without any problems on a single A4 sheet of text.
Design is thinking made visual.
No freezing up here. XP Home SP3 RC2
-=Bob=-
Page of text any size in text boxes linked or just free text filling a page with or with out text flowing round objects (repelling), applying clip view no problems.
Xp pro sp2 / 4gig ram / athlon dual core
Derek
Last edited by masque; 20 April 2008 at 11:31 AM.
"Come in out of the dry and wet yourself by this tap". Spike Milligan
http://www.xaraxone.com/FeaturedArt/mar07/
http://www.xaraxone.com/FeaturedArt/aug10/
http://www.xaraxone.com/FeaturedArt/dc2/index.htm
No freeze up here,
1,3 ghz,1,5 gb ram Xppro sp2
Hans
Works just fine here (Vista SP1). You say it happens when clipping large amounts of text. How many characters/words are that? I presume it does not happen with just a single paragraph? Any unusual font being used? Could you (or Wolfgang who sees this problem as well) please provide a test file, i.e., the state of the file just before you press "Q"?
I have tried it with all different types of text objects and do not see any problems here.
Martin (Xara text developer)
Yes this happens with me as well.
XP home, SP3 ,Athlon 2.2 with 2gig ram.
I will try and post the file.
http://www.talkgraphics.com/attachme...1&d=1208695836
I can't save the file because Xtreme locks up so I've posted a screenshot.
Last edited by Zenarcher; 20 April 2008 at 12:30 PM. Reason: Added screenshot and explanation.
Ah, now I see. I bet you put the rectangle in FRONT of the text. So, instead of clipping the text to the rectangle (which is easy), you end up clipping the rectangle to the text. So, you are asking Xtreme to use thousands of shapes as a clipping path, which requires all of them to be unified first. I am not surprised that that takes some time. That already went wrong in 3.2.
Can the others that see the bug check that this is the cause of their problems, too? So, the solution is to bear in mind that when pressing Q, the bottommost object is used as the clipping path. You would not normally want to use the union of thousands of shapes as a single clipping path.
Martin (Xara text developer)
Ahhh. Although I was one who didn't have this problem I tried it with the rectangle on top anyway. It caused Xara to go cuckoo and resulted in these two msgs (I didn't send the error report). Then it closed and everything was fine. No other open prgs were affected.
-=Bob=-
Martin,
you are right.
When I put the rectangle to the back, it works perfectly, no freezing or anything.
At first, I did just as hombudsmann wrote and of course this is the "wrong way around".
I don't know if there is any real way avoiding this (you could do that by accident and lose your work after that).
Maybe some kind of warning, that this could take a long time or may not work as expected?
I don't know if this would ever happen to me in real life, but if so I would be p*ssed when it crashes.
Wolfgang
Bookmarks