Issues with vaSpaces


  • When the text box inside of a vaSpace is big enough that it cuts the space into parts, the hatching is incorrect, and the space is not correctly calculated - see screenshot.
    The middle space is named ‘B’, but it is not listed in the table.

  • We talked about this: a vaTable should be placeable into the Layout space. It is already, with the ‘ChangeSpace’ command trick.
    However, the vaUpdate command does not work there. Since it is possible to force a refresh of the table by simply changing the ‘style’ parameter to something else and back, this restriction does not make any sense.
    Will be possible in VA3?
    Thanks a lot!

Hi @Eugen,

I could reproduce the problem with the hatch, but not the fact that it is not included in the table. Please, could you send me that file?

We are redefining how tables work in VisualARQ 3. I’ll add this to the list.

that the tables can be exported to obsidian and that each value, rows or columns can be automatically labeled to make a second brain of each project, that would be great and unique, the first BIM that can make a second digital and flexible brain

1 Like

Hello @miguelayora3,

Why do you think it would be useful to have this data in Obsidian? How would you use it once you have it there? I don’t have a lot of knowledge about this software, so I am curious to know which workflow you would follow with it.

1 Like

1.- there are many people who do not have programming knowledge and would like to have that knowledge to customize their tools with respect to the information that is generated and achieve their goals and obsidian can easily do that (each geometric element is text information in its interior and each text information is ordered and related in obsidian)
2.-the part of obsidian graphs is very powerful since we can have a quick reading filtered by a specific tag
3.-the metadata of each geometric element is very important since each geometry has standard and personalized data that will be accumulated and used for later evaluation
4.-an accumulation of metadata can be made in each project carried out, for example, if you are working with a team of people, they would have access to the elements used in previous projects and filter them, it does not matter if the team members are new, they are in knowledge of the elements that have been used throughout the history of the second brain created
5.-if an element is filtered by cost and by measure placed in a certain project or in a current project, it can be easily found and how it is related to other elements, this would allow time, budgets, etc. to be optimized each time.

1 Like

Hi @miguelayora3,

I have been making a research about Obsidian and I think it can be very useful to share knowledge in a team through time. I’m still not sure about how this export could be made… maybe instead of tables, we should export directly parameters to a csv or txt file? This way you would have all the data exported and you would miss nothing.

How should this data be ordered in the exported file? It should be exported in a way Obsidian or any other similar software understood it.

I guess there should be a way to export data for one single object, for many objects selected, or for the whole fie…

1 Like