Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot find EcsComponent in namespace Invert.uFrame.ECS #2

Open
grofit opened this issue Apr 27, 2016 · 10 comments
Open

Cannot find EcsComponent in namespace Invert.uFrame.ECS #2

grofit opened this issue Apr 27, 2016 · 10 comments

Comments

@grofit
Copy link

grofit commented Apr 27, 2016

Seem to get an error when trying to build on an empty project with a single component, here were the steps:

  • Create a new project
  • Downloaded and unzipped repo into assets
  • Create a new module
  • Add component called Buffable (could be anything, it had no content in it)
  • Pressed the build button

Then got the error:

Assets/Plugins/Editor/uFrame.ECS.Editor/Components/Buffable.cs(24,48): error CS0234: The type or namespace name `EcsComponent' does not exist in the namespace `Invert.uFrame.ECS'. Are you missing an assembly reference?

I am using unity 5.3.4f and like I say it is a new project with nothing but this repo, when opening the generated code in VS it appears that the namespaces generated are wrong or have been refactored somewhere.

@mkuhr
Copy link

mkuhr commented Apr 28, 2016

Only on Github version: Not for the Unity Asset. We have the uframeECS Architect and Editor sources so on default one of those is open.

Thats how you use it :

  1. Open any workspace and import once or the next step will not work. Basically the Dialogue has to disappear.
  2. You have to create a new database first, when you pull from Github. For that click "Database" in the lower left corner ofh the uFrame Graph Window and choose "Manage"
  3. Click on "New Empty Database". Choose a name and leave Codepath as is
  4. Create Workspace with your name
  5. Create Module with your Project Name
  6. Have fun. Create components, systems, events.....

@grofit
Copy link
Author

grofit commented Apr 28, 2016

So based upon this I would probably say it should default to not being in a DB so you start at the "Make a New Database" screen, as unless you know the tools and have read this message you will probably end up doing what I did and think "it doesn't work"

@mkuhr
Copy link

mkuhr commented May 9, 2016

Easy and fast solution proposition:
Change Assets\Plugins\Editor\uFrame.Editor\Systems\DatabaseService.cs

in line 65 from

var dbDirectories = Directory.GetDirectories(path,"*.db",SearchOption.AllDirectories);
to
var dbDirectories = Directory.GetDirectories(path,"*.db",SearchOption.TopDirectoryOnly);

Easy start for using ECS. With the normal flow that we know from the Unitypackage.

Pro Users can undo this to make the ECS Database visible in the uFrame Grapheditor to change the implementation?

@grofit
Copy link
Author

grofit commented May 9, 2016

I dont know the knock-on effects this would cause but as long as it makes workflow for getting started with ECS easier and error free then I would go for it.

👍

@micahosborne
Copy link
Owner

This would only allow databases to be created/used in the root directory. You really just need to create another database and ignore the ECS database. I get that might be confusing, but hey didn't you learn from it? :p

3 similar comments
@micahosborne
Copy link
Owner

This would only allow databases to be created/used in the root directory. You really just need to create another database and ignore the ECS database. I get that might be confusing, but hey didn't you learn from it? :p

@micahosborne
Copy link
Owner

This would only allow databases to be created/used in the root directory. You really just need to create another database and ignore the ECS database. I get that might be confusing, but hey didn't you learn from it? :p

@micahosborne
Copy link
Owner

This would only allow databases to be created/used in the root directory. You really just need to create another database and ignore the ECS database. I get that might be confusing, but hey didn't you learn from it? :p

@grofit
Copy link
Author

grofit commented May 10, 2016

You are welcome to class it as closed and just put it down as a documentation step, or just ignore it completely, I am just aware that most people looking to try it will probably fall over at the first point without knowing this first.

@mkuhr
Copy link

mkuhr commented May 10, 2016

I agree with grofit. Thats not user friendly enough. Too many people will just abandon it at this stage, when they are trying it out. And this first experience doesnt live up to this fantastic product.

Had to edit my "making it work" above, because you even have to open and import a workspace before manage database window shows up when you click it.

Whats wrong with having databases at the root directory for starters?

Or can you point me to a solution where i can have all Directories searched, but show the "Create New Database Window" without having to open any workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants