Any news from the development front?

Does anybody know what's going on about the next release of X¹ (or X², maybe) and when it is due? There are still plenty of bugs to fix (some are quite old) and many requested features to add -- just browse this forum.

Some months ago many of us were led to believe that upgrading to X¹ would help change things this time, and we all did it. However it seems that things are just the same. I don't want to wait four more years for another small update with a new name. Do you guys have the same impression, or is it just me?

Does anybody know what's going on about the next release of X¹ (or X², maybe) and when it is due? There are still plenty of bugs to fix (some are quite old) and many requested features to add -- just browse this forum.

Some months ago many of us were led to believe that upgrading to X¹ would help change things this time, and we all did it. However it seems that things are just the same. I don't want to wait four more years for another small update with a new name. Do you guys have the same impression, or is it just me?

Hello Rubem,

I feel x1 is a good baby step. It takes time to do good coding, particularily when you are breaking new ground. http://www.talkgraphics.com/images/smilies/biggrin.gif

Development is under way for the next release but I have not heard anything as to when it will be. My guess is sometime in the first half of 2005.

Gary

Rubem, there's never a shortage of ideas. Working out which ones are realistic, which ones will enhance the product and which ones are doable is another thing!

But as the post at the top of the Xara X forum says, we're after a developer. Xara X is a product we're developing. It certainly won't be four more years. http://www.talkgraphics.com/images/smilies/smile.gif

Is there a planned feature list which may, at least in part, be made public?

My main gripes with Xara X is lack of accuracy, lack of a treeview with drag and drop for groups and clipviews, and lack of a mesh fill tool.

In a word, no. As you can appreciate, when software is being developed features are dropped or delayed, features are added etc. Although a plan is always made, nothing is ever set in stone. The same goes for a release date.

So to avoid "You said XYZ would be in it" and "You said it'd be released on XYZ" we don't give give specific details.

However I'm sure once again TalkGraphics will be the first to hear of any developments.

<BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>So to avoid "You said XYZ would be in it" and "You said it'd be released on XYZ" we don't give specific details. <HR></BLOCKQUOTE>I am also a software developer. I don't fear complaints from users. On the contrary, I learn from them and try to keep them satisfied as much as I can. I understand your point of view, but Xara X never made it because of this won't-disclose-anything attitude, too few updates, and the overall "abandonware" feeling that is still fresh in our memories.

The good news is that we have these wonderful people here at this forum. Without them Xara X would be dead already. Hats off to them.

hi Rubem,

A little harsh aren't we? http://www.talkgraphics.com/images/smilies/biggrin.gif

No tailoring to the printers(macs) is what is stifling xara. Your "Abandonware" comment is totally untrue... IMHO http://www.talkgraphics.com/images/smilies/wink.gif

Not even close to abandonware. I have had xara for a year now and really started using about 6 months ago, the popularity and publicity for xara has been going up in leaps and bounds. The only people that I've seen not like it are people that go in close minded and mac users that are mad because that can't use it. http://www.talkgraphics.com/images/smilies/tongue.gif http://www.talkgraphics.com/images/smilies/biggrin.gif

I sometimes show my students what Xara is capapble of. They are often impressed by its speed. Illustrator sucks and they all know that, but I can't whole heartedly recommend Xara to anyone until they resolve file format import and export issues.

It's unfortunate, because I'm in a good position to recommend Xara to people who could easily become die hard Xara users, but I want to spare them the file format nightmares that I have dealt with.

But Xara in the hands of anyone who knows how to use it will blow away people who are accustomed to Illustrator.

Of course I'm being harsh. I have no doubts about the worderful capabilities of Xara X. I use it since 1996 (I think it was called CoreXARA 1.1 at that time) and I also use it for classes. The problems I point out are related to old bugs (Look here for an antique), old omissions, and old attitudes. If you had to wait four years for a couple of minor tweaks (with many bugs still there) you would know what I mean.

Hello Rubem,

I have been using xara since 1996 also. And yes it has a few things that could be improved, but it is 10000 times better then the other choices out there. If you are bugged by it so much you can always use pcpaint by microsux. http://www.talkgraphics.com/images/smilies/biggrin.gif

Well, if crashes when moving objects between layers and 8-year old bugs are considered minor, then I give up. Honest! I won't be the only one complaining while everyone else is happy. http://www.talkgraphics.com/images/smilies/confused.gif

Ummm... Rubem,

I have moved thousands of objects at one time from one layer to another and have never had a crash. I have rescaled objects across layers with no problems. that is a new bug on me.

Would you mind explaining how you can reliably duplicate this "bug"?

<BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>Originally posted by John Rayner:
I have moved thousands of objects at one time from one layer to another and have never had a crash. <HR></BLOCKQUOTE>Never had a crash using Xara? You must be kidding...

<BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>Would you mind explaining how you can reliably duplicate this "bug"? <HR></BLOCKQUOTE>Sure, here it is -- without the quotes. You don't need thousands of objects, just about three are enough. Just open this file, create a new layer, drag the new layer to above Layer 1, select all, move to layer and there you go -- Xara crashes miserably. Just one of my favorite oldies...

Hi Rubem,

I opened your file and followed your instructions. I couldn't make it crash on my system. The file as it opens has 2 layers. Am I to make a third layer and move the objects with the move to layer buttons? If so, I am able to move these objects back and forth through all three layers with no problem.

If no one else can duplicate this crash then the problem might be with your system.

<BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>Originally posted by Sheffield Abella:
I opened your file and followed your instructions. <HR></BLOCKQUOTE>Are you sure you changed the layer order prior to moving the objects? You must drag Layer 3 (the one you just created) in the Layer Gallery so it sits between Layer 1 and Layer 2, then move all objects to Layer 3.

Sheff and John,

Rubem is showing one of the most horrible bugs (IMO) that Xara X has. It has been reported by many people on X and X1... I'm sure they are working on it at the Xara mansion, but right now I don't trust the move between middle layers, so I don't use use it all... http://www.talkgraphics.com/images/smilies/frown.gif

It's very easy to replicate:
(a) Open a new document
(b) Draw two elipses on your "layer 1"
(c) Create a layer 2, and draw a rectangle on it...
(d) Create a layer 3, and then move this layer so it's between layer 1 and 2...
(e) Select all (Ctrl+A) - and with layer 3 selected - hit "move..."

Xara X freezes, and the only way to get your PC back is to rip the powercord out of the wall with your feet... or to reach over and hit the reset button... http://www.talkgraphics.com/images/smilies/tongue.gif

I will have to test this. I have never ran into that particular crash/bug. I have made it crash a multitude of different ways, but never by playing with layers. Most of the time, by pressing the outside of the envelope tho.

I shy away from brushes, because of that very reason... I push it too far and out to lunch it goes.

I have had every other piece of software crash and burn, much eaiser than any version of xara.

Risto,

I am doing it exactly step by step as you have written and I can't crash it. This works on my machine.

Doesn't crash for me either...

I can't duplicate this either. In all the years I've used Xara I cannot remember one occasion of layers causing a crash, and I use a great deal of layers.
Egg

I was able to duplicate the crash on my machine. I didn't have to pull the power cord to continue but it did take several minutes for Windows to close Xara X which was Not Responding.

dafipp

Hello

I don't have a problem either.
I made four layers and moved the layers up and down and moved objects between layers.
I use a Matrox Millenium G550 with XP pro.
It could be a video problem.


Mike Engles

I agree that this might be a hardware incompatibility issue.

We should all list our hardware so we can narrow down what this error is.

Mine:
CPU: AMD 3200 (underclocked to 2500)
MB: K7N2 Delta-ILSR
OS: WinXP Pro Sp2
Video Card: AIW 9700
Memory: 1 Gig Corsiar 3200
HD: WD 250G C:OS D:Apps E:Scratch/Temp X: Data

Mike,

I don't have a problem creating or moving objects between layers either. This error only happens when you move 'all' objects (but only in a situation like the one Rubem and I described.)

However, it did occur to me that I'm not running the latest build of X1. Then again, it seems to happen to at least two other people as well...

I'm curious - for you that don't have the problem, and still have Xara X installed, could you try on the older software as well?

I have had it installed on two different machines, with the same crash. I reported it during the Beta testing as well - and it was replicated by Xara.

I have reproduced this error on two distinct systems; one a Pentium 4 and the other an AMD Athlon XP. Below are some of the details from Microsoft's System Info utility.

OS & SYSTEM INFO
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 1 Build 2600
System Manufacturer Dell Computer Corporation
System Model OptiPlex GX270
Processor x86 Family 15 Model 2 Stepping 9 GenuineIntel ~2792 Mhz
Total Physical Memory 512.00 MB
Available Physical Memory 225.36 MB
Total Virtual Memory 1.72 GB
Available Virtual Memory 1.20 GB
Page File Space 1.22 GB
VIDEO (on board)
Name Intel(R) 82865G Graphics Controller
PNP Device ID PCI\VEN_8086&DEV_2572&SUBSYS_01511028&REV_02\3&172 E68DD&0&10
Driver c:\windows\system32\drivers\ialmnt5.sys (6.14.10.3762, 665.50 KB (681,469 bytes), 2/10/2004 12:17 PM)

OS & SYSTEM INFO
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
System Manufacturer soyocomputer
System Model K7VME
Processor x86 Family 6 Model 10 Stepping 0 AuthenticAMD ~2163 Mhz
Total Physical Memory 768.00 MB
Available Physical Memory 464.93 MB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 1.76 GB
VIDEO (on board)
Name VIA/S3G UniChrome IGP
PNP Device ID PCI\VEN_1106&DEV_7205&SUBSYS_10FDA723&REV_01\4&1FE B96E4&0&0008
Driver c:\windows\system32\drivers\vtmini.sys (6.14.10.0123-16.94.39.06, 134.63 KB (137,856 bytes), 7/9/2004 8:23 PM)

I confirm Risto'S last posting. It has to do with the MOVE button function in the Layers Gallyery.

JUST TO PLAY IT SAFE. DON'T USE THE MOVE BUTTON!

MY WORKAROUND IS TO CHANGE THE ACTIVE LAYER TO THE ONE YOU WISH TO MOVE YOUR SELECTED OBJECTS TO. THEN CTRL+X (CUT), FOLLOWED BY CTRl+SHIFT+V.

Risto et al,
I didn't specify this in my earlier post but I am still using the old version - Xara X.

CPU: AMD Athlon 950
MB: Gateway
OS: WinXP Pro Sp2
Video Card: 3dfx Voodoo5
Memory: 640 Mb
HD: WD 80Gig everything is on C: drive

dafipp

Alright, after reading John Clements post I have been able to reproduce the error. The buttons I was using are move to layer in front and move to layer/frame behind. These buttons work fine.

I wasn't using the move button in the layers gallery. I've never used this button in the past and I didn't even know it was there. This is the button that causes the error.

But I agree, don't use the button until it's fixed.

So at this point, my hard drive is working over time while Xara tries to resolve this command.

Hello

Looks like I can now reproduce the bug.
I made another layer(30 and a elipse in the layer.
Moved the layer between layers 1 and 2. Select the middle layer. Selected all the objects and used move to move the objects into the selected layer.

I have to say it is a very esoteric bug, but I don't use layers that much.
Eventually Windows closes Xara, no need to reboot.

Mike Engles

sorry guys,

Can not duplicate bug... I followed Risto's instructions to the letter. Xara X1 running like a champ...

AMD E amchine POS...

YES. Using the MOVE button I can reproduce the bug. Never used this button before. As it closed down I got a virtual memory to low warning as well.
It would appear that the problem is caused by moving objects in 2 directions at once. ie up & down.
As I use a lot of Layers, but never use this button, I can see why I've never encountered it before.
Egg

Geez guys, what the heck are you doing? Is there anything else than bug sniffing you'll do with Xara X? ;-}

No, I can't reproduce the bug. Whatever I select and move between any layers (clip view objects, vectors, bitmaps) won't crash of freeze Xara.

I mean I'm not looking for bugs, I'm using Xara as a tool for my projects, and it just works great. If you complain about a move-between-layers-bug: select your objects you want to move, cut, activate new layer, paste at same position, done.

I've set up my basic template with 10 layers plus the guides layer. The only weird thing I've noticed is that sometimes imported objects are stuffed into layer 10, though layer 01 is the active one. So I just move the objects to layer 01 and continue to work, not to move layers all day long, because I have to meet deadlines ;-}

Thumbs up!

what is being determined here is that
when a simple operation is run in the layers
palette theres a crash being replicated
on several systems, so obviously the problem
exists, its not a ufo sighting by one person.
Reputable companies (like Xara) ofcourse will
attend to these for their customers freedom
in designing and workflow in
anyway the software allows/supposed to allow.
reporting bugs is critical to software
improvement and always worthy of attention.

Jens,

There is no bugg sniffing needed... The problem has been there since Xara X (which stinks... http://www.talkgraphics.com/images/smilies/tongue.gif http://www.talkgraphics.com/images/smilies/wink.gif )

Jens: "Whatever I select and move between any layers..."
--- That's not the bug... It's described in Rubem's and my previous posts (and clarified by Mr. Clements).

Xara Ltd. replicated it during the beta testing, so obviously it's there.

The error described is simplified... It can also happen in other sitations as well, when moving objects from layers, above and under your current one, simultaneously. Your safest bet is to deal with one layer at a time.

I'm sure Xara X is working on it. Also, John Clement's workaround accomplishes the same thing.

I tried submerging my PC overnight in a bathtub full of gasoline while Xara was running, and, sure enough, Xara crashed. Anybody know of any work-arounds for this one? http://www.talkgraphics.com/images/smilies/biggrin.gif

.joroho.

Joroho,

The work-around is to duct tape a dryer hose to your PCs fan outlet, and place the case itself in a couple of garbage bags before suberging the whole thing. Xara will run well - until you start merging layers using the feature and button, designed for that very purpose... http://www.talkgraphics.com/images/smilies/wink.gif

"Anybody know of any work-arounds for this one?" Joel

As the wise physician once said... "Don't do that".