Obvious Bugs in Xcos

Specific domains Xcos
1

Hi there,

here are the two bugs that should be so obvious that probably you already know:

  1. When I copy and paste an Xcos model (all select, CTRL+C, CTRL+V) the connections lines are multiplied three fold. All lines are perfectly mathing each other so it’s not possible to see the issue. When runnig the model, I get an error about port dimensions.
  2. When a block is already selected and I want to select only a line, the block remains selected. I expect the block to be deselected when selecting something else.

Are there some fixes for those?

Many thanks
Alex

2

Since nobody replied, I’ll add a few more:

  1. When using a super block with a mask of parameters, if the mask is removed (e.g. to edit the block diagram inside) and then I run the simulation, the results are wrong but no error or warning is issued. As soon I restore the mask, the simulation results are as expected. Some other times, the simulation simply takes forever, also no error.

  2. Having to remove the mask, close the window, restore the mask costs at arround 5 clicks. When experimenting with often changes to the content of the mask it really annoying. To be able to leave the mask content opened while running the next simulation would be nice. In general it would be nice to have a context menu entry for simply editing the content of the mask, the model itself.

3
  1. Very often, basically always, after closing an then reopening an xcos model, the connection lines between blocks get additional middle points that are randomly positioned. You get a zig-zag of lines all interesection arround the plane.
  2. When deleting a block, the lines connecting to the block are also deleted. That shouldn’t happen. Often I just want to replace a block by another one (e.g. a super block) and want to quckly reconect the lines to the block ports again. Due to the line deletion, I must drag all the connection lines again.
4
  1. Leaving an input port unconnected leads to error. Why not assuming scalar zero as default input and then issue errors if still the case?
5
  1. In the summation block the +/- signs disappear and I must open and close the block parameters in order to find out if there is + or - there.
6
  1. When using “Save as” function for an .zcos model and the type selected in the dialog window is “zcos”, I still have to enter the model name as “name.zcos”, otherwhise the model is not saved and the title bar of the model shows the ending “.ssp”. No new file is created! No warning is generated. Everything look like it was saved. If you don’t know this, you can work on this model and after closing it, your work is lost!
7

Hi Alexandru,

Thanks for posting your coments. Could you report these as issues on Gitlab ?

Some are already fixed (not released yet) and others might be discussed before impelmentation.

Thanks

8

Hi David,

I suppose I can, but is it a good idea to post all 9 points as one ticket or should I post 9 different tickets?

9

Please post individual issues, you will then be notified when a fix will be merged and the associated release.

Some of your reports also are subject to discussions, it will be simpler to keep the discussion on a single issue. If you have programming knowledge, you can also propose a fix.

10

Done!
I could get used to this.
I think I have another bunch of issues I could think of…

11
  1. When the xcos model lies on a network mounted drive, nothing works, you get weird errors but nothing related to the actual problem. So currently you must run the model from e.g. C:/.