macoslib producing an error message.

Targets macOS
1

Hi,
I just dragged in the latest macoslib folder into the navigator, and tried to run my app, but received the error message in the screenshot below.

Does anyone have any idea what I need to do to correct this? I am also using RetinaKit which may be causing the conflict???
I am using the latest version of Xojo, OS X, and macoslib (if that helps).

Thanks.

2

Is that the latest version from GitHub ?
If not I believe this issue has been resolved in that one if you go grab a new copy

3

Norman - I am using the latest version from their Github - I grabbed it 10 minutes before posting here :frowning:

I presume there is only 1 repository for this?
This is the URL I just got it from: Link Here

4

The compiler is very accurately telling you what the problem is. There is a global structure named CGInterpolationQuality in the CoreGraphics module and there is a global structure named CGInterpolationQuality in the HIDPI module.

5

Yes, but unfortunately the compiler isn’t very accurately telling me how to correct the issue - and it appears it isn’t as simple as renaming one of them - hence my original question :frowning:

6

I would try making RetinaKit’s version protected or deleting it.

7

I will try that - thanks.

8

Oh no - I just tried protecting the RetinaKit version, but it seems to be locked / encrypted?

9

[quote=190224:@Richard Summers]Oh no - I just tried protecting the RetinaKit version, but it seems to be locked / encrypted?
[/quote]

You should ask the original author of those HIDPI classes not to pollute the global namespace, but for now you can probably change the scope of the version in macoslib.

10

The HIDPI class is from Sam’s RetinaKit - I will try to see what the current situation is.
I will now also try changing the scope of the macoslib version.

Unfortunately - this is why I gave up software development about 4 months ago. Trying to get Xojo, RetinaKit and Yosemite to play nicely together is mind boggling :frowning:

11

Nope, the same error is produced if I try changing the scope of the macoslib version.

It seems this is a showstopper then. I can’t delete macoslib, otherwise certain features will not be available, and I can’t remove RetinaKit, otherwise the app will not be Retinafied :frowning:

Thanks anyway.

12

This is one reason we are using a namespace for everything in the new framework
So we dont cause this kind of issue in your projects

13

[quote=190234:@Richard Summers]Nope, the same error is produced if I try changing the scope of the macoslib version.

It seems this is a showstopper then. I can’t delete macoslib, otherwise certain features will not be available, and I can’t remove RetinaKit, otherwise the app will not be Retinafied :frowning:

Thanks anyway.[/quote]

You could just delete the one in macoslib.

14

I have also tried deleting the macoslib one, but then I get another error:

This error message tells me “there is no class with this name” - but doesn’t actually tell me what the name is? Or does “Code” refer to the missing class name?

I have contacted Sam so hopefully he may be able to shed some light regarding this particular error message.

15