L Gutman94

Created March 24, 2018 18:01

Hierarchical tables: The repo should be up to date - you are welcome to take a look.

1. Community
2. MPS
3. Hierarchical table - how do I set up customized behavior?

• 0 votes

Created March 22, 2018 11:31

Hi, I've given up on trying to use a hierarchical table and used a regular table instead. However, I'm still interested in a solution based on hierarchical tables. I'm sure it's a lot more elegant ...

1. Community
2. MPS
3. Hierarchical table - how do I set up customized behavior?

• 0 votes

Created February 20, 2018 17:18

I've been trying that as well, but it never worked until I got rid of all usages of and dependencies to "mpstools" in "Timekeeping" and then added them again manually. Anyway, it's resolved now.

1. Community
2. MPS
3. Elements from imported language "out of search scope"

• 0 votes

Created February 20, 2018 17:12

The problem was that I've already separated the two languages before making this forum post (as I mentioned before) and have done some further work on "mpstools". So I couldn't just start over wher...

1. Community
2. MPS
3. Elements from imported language "out of search scope"

• 0 votes

Created February 20, 2018 16:44

I did it a bit differently when I separated the languages (it was before I made this post). I didn't move "timekeeping" into a separate project - I moved "mpstools".

1. Community
2. MPS
3. Elements from imported language "out of search scope"

• 0 votes

Created February 20, 2018 16:34

"mpstools" is in the project because I added it to the project path, as you suggested.

1. Community
2. MPS
3. Elements from imported language "out of search scope"

• 0 votes

Created February 20, 2018 15:28

I've already separated the two languages. I also added the utility language to the project paths and to the project library: It still can't resolve the reference:

1. Community
2. MPS
3. Elements from imported language "out of search scope"

• 0 votes

Created February 20, 2018 12:17

The utilities language is kept in a separate directory. I just tried what you suggested, removed the model root and added the utility language as a global library (first, I tried to use the path of...

1. Community
2. MPS
3. Elements from imported language "out of search scope"

• 0 votes

Created February 20, 2018 10:54

I just tried it and it didn't solve the problem. Also, strangely enough the language will actually build (if I ignore the errors) and the UI elements (editor components) from the utility language w...

1. Community
2. MPS
3. Elements from imported language "out of search scope"

• 0 votes