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

Issues when just using #include <Qtilities> #76

Closed
JPNaude opened this issue Jan 9, 2013 · 0 comments
Closed

Issues when just using #include <Qtilities> #76

JPNaude opened this issue Jan 9, 2013 · 0 comments
Assignees

Comments

@JPNaude
Copy link
Owner

JPNaude commented Jan 9, 2013

Here is a short discussion related to this issue:

  1. Not sure what the intention with the Qtilities #include is in /include, but it doesn't seem to pull in . i.e. #include is not sufficient for using Qtilities.
    I've not run into problems with this, but I was wondering if it might be a namespace issue. Are you using the following after the include?

"using namespace Qtilities;"

If so, I think this commit will fix that. If you are still getting it, please let me know and also then try the following please:

"using namespace QtilitiesCoreGui;"

The problem is that if I do:

include

using namespace Qtilities::CoreGui;

It doesn't find the Qtilities::CoreGui namespace (main.cpp(22): error C2039: 'CoreGui' : is not a member of 'Qtilities'), which is where QtilitiesApplication lives. Which is why I thought the include was just not pulling in . If I do:

include

using namespace Qtilities::CoreGui;

It works fine.

With the latest version

include

using namespace Qtilities;
And

include

using namespace QtilitiesCoreGui;

Bot result in namespacing issues, the former when using QtilitiesApplication, the latter can't find QtilitiesCoreGui.

@ghost ghost assigned JPNaude Jan 9, 2013
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

1 participant