Welcome, Guest. Please login or register. Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - AshleyF

Pages: [1] 2
1
Dear All,

I have found what I think may well be a bug in SFML 2.4.2 on macOS 10.13.3.

I want to be able to switch between different fullscreen resolution rates by pressing a button during the application's execution.

The following source code was taken and adapted from a forum post by Raptor88.

int main()
{
    std::vector<sf::VideoMode> modes = sf::VideoMode::getFullscreenModes();
   
    size_t mode = 0;
    sf::RenderWindow Window(modes[mode], "SFML Sample Application");
   
    while (Window.isOpen())
    {
        sf::Event Event;
        while(Window.pollEvent(Event))
        {
            switch (Event.type)
            {
                case sf::Event::Closed:
                    Window.close();
                    break;
                case sf::Event::KeyPressed:
                    if (Event.key.code == sf::Keyboard::Escape)
                    {
                        Window.close();
                    } else if (Event.key.code == sf::Keyboard::F2 && mode < modes.size() - 1)
                    {
                        Window.create(sf::VideoMode(modes[++mode]), "Mode", sf::Style::Fullscreen);
                    } else if (Event.key.code == sf::Keyboard::F1 && mode > 0)
                    {
                        Window.create(sf::VideoMode(modes[--mode]), "Mode", sf::Style::Fullscreen);
                    }
                    break;
                default:
                    break;
            }
        }
       
        Window.clear(sf::Color(0, 255, 255) );
        Window.display();
    }
   
    return 0;
}

This code appears to work fine on the PC, but not on the Mac.

The Mac shows the correct dimensions of the created window, but as a borderless window centred around the middle of the screen with a black border around it. The window doesn't stretch to cover the entire screen.

If anyone can please offer some advice concerning this, I'd be most grateful.

Kind regards,

AshleyF


2
Feature requests / MoltenVK
« on: February 28, 2018, 03:09:48 pm »
Dear All,

As MoltenVK has become available on github, I was wondering what prospect Vulkan now has of becoming part of SFML?

Kind regards,

AshleyF

3
General / Possible Mac 2.4.2 Bug - 'Month 13 is out of bounds'
« on: December 07, 2017, 07:14:11 pm »
Dear All,

Starting this December 2017, an error message appears in Xcode even with just the source code listed below:

#include <SFML/Graphics.hpp>

int main(int, char const**)
{
    sf::RenderWindow window(sf::VideoMode(800, 600), "SFML window");
    return EXIT_SUCCESS;
}

The error message in the Xcode project I called 'Timer Error' is as follows:

2017-12-07 17:56:57.696036+0000 Timer Error[13769:8570286] Month 13 is out of bounds

Any suggestions for fixing this error message will be most gratefully received!

Kind regards,

AshleyF

4
General discussions / Re: VS 2017 Static & Dynamic problems with 2.4.2
« on: August 01, 2017, 06:22:01 pm »
Dear eXpl0it3r,

Thanks very much for your most excellent and helpful video!

It's all working now!

Thanks again for all your help.

Kind regards,

AshleyF

5
General discussions / Re: VS 2017 Static & Dynamic problems with 2.4.2
« on: August 01, 2017, 04:19:41 pm »
Dear eXpl0it3r,

Thanks very much for you reply.

Unfortunately, after trying everything you suggested, and checking and verifying everything you specified, it still isn't working :(

Any advice would be most gratefully received.

Kind regards,

AshleyF

6
General discussions / Re: VS 2017 Static & Dynamic problems with 2.4.2
« on: August 01, 2017, 12:29:34 am »
Dear eXpl0it3r,

From the VSC 2017 SFML build I downloaded that you made, there are two folders containing the relevant files.

I've tried each folder under both build options and still get the same error.

Any suggestions would be most gratefully received.

Kind regards,

AshleyF

7
Dear JayhawkZombie,

Thanks for the suggestion.

Although the linker error count has now come down to 33-ish, the new error being reported is:

LNK2038   mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MDd_DynamicDebug' in main.obj

Any suggestions would be most gratefully received.

Kind regards,

AshleyF

8
Dear All,

After reconfiguring the preferences in accordance with the advice given, I have discovered that:

1) A release build can compile, link and execute; but

2) A debug build cannot compile due to linker errors.

The error messages start with:

LNK2038 mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in main.obj

Any advice will be most gratefully received!

Kind regards,

AshleyF

9
Dear JayhawkZombie,

Thanks very much for your reply.

Other than opengl32.lib, winmm.lib and gdi32.lib, all of the other libs are present.

After searching the hard drive and finding that they are not present, I googled for an answer.

It appeared to be the case that I'd need to install the latest Windows SDK.

I did that, and those libs still are not present anywhere.

Any advice would be most gratefully received.

Kind regards,

AshleyF

10
Dear eXpl0it3r,

Thank you very much for your reply.

After downloading your nightly build and repeating the installation, I have discovered that:

1) The dynamic configuration works absolutely fine; but

2) The static configuration does not compile.

I have used both the 'lib' and 'static-std' in the project configuration setup and always receive the following compiler error message, this being the first one, with many others along the same lines:

LNK2019 unresolved external symbol __imp__wglShareLists@8 referenced in function "private void __thiscall sf::private::WglContext::createContext(class sf::private::WglContext *)" (?createContext@WglContext@priv...

and so the error message continues.

Any suggestions to overcome this problem would be most gratefully received.

Kind regards,

AshleyF

11
General discussions / VS 2017 Static & Dynamic problems with 2.4.2
« on: July 26, 2017, 07:39:01 pm »
Dear All,

I am having major problems with VS Community 2017 and 2.4.2 32-bit.

I follow the installation instructions to the letter, but it just will not work.

I've used CMake on the 32-bit source code, but that also doesn't work.

Does anyone happen to have any idea when a VSC 2017 specific stable release will be available please?

Kind regards,

AshleyF

12
Dear Webmaster,

Is it possible to get the website to send an automated email to every registered SFML user when a new stable release is available for download?

This would help keep everybody up-to-date with SFML and I'm sure everybody would be delighted to receive this notification! ;)

Kind regards,

AshleyF

13
Feature requests / Re: Joystick problems on the Mac
« on: July 01, 2017, 03:20:39 pm »
Dear Hiura,

Fantastic news! Other than one exception, all now seems to be working fine!  ;)

The exception is the Thrustmaster Dual Analog 4 V.1.

For some strange reason, the right thumb controller only works horizontally, and not vertically.

The error in the output window is as follows:

Unexpected usage for element of Page Generic Desktop: 0x1
Unexpected usage for element of Page Generic Desktop: 0x36
Unexpected usage for element of Page Generic Desktop: 0xbb
Unexpected usage for element of Page Generic Desktop: 0xbb
Unexpected usage for element of Page Generic Desktop: 0xbb
Unexpected usage for element of Page Generic Desktop: 0xbb
Unexpected usage for element of Page Generic Desktop: 0xbb

By way of information, there are the occasional 'Unexpected usage ...' error messages with various other joysticks even though they work with the new code.

Please let me know what you'd like me to try next.

Thanks very much for the excellent code update!

Kind regards,

AshleyF

14
Feature requests / Re: Joystick problems on the Mac
« on: June 30, 2017, 02:44:18 am »
Dear Hiura,

I have obtained the following outputs:

Name: Wireless Controller, Vendor ID: 0x54c, Product ID: 0x5c4
Unexpected usage for element of Page Generic Desktop: 0x5
hat?
Null State? true
Preferred State? true
Is Linear? true
Is Wrapping? false
Is Relative? false
Is Array? false
Is Virtual? false
Collection Type: 0 (based on IOHIDElementCollectionType)
Logical Range: [0, 7]
Physical Range: [0, 315]
Value: 360/360
Raw value: size -> 1 data -> 8

Irrespective of how the joystick is being used, these results are constant.

Hope this helps!

AshleyF

15
Feature requests / Re: Joystick problems on the Mac
« on: June 29, 2017, 08:18:00 pm »
Hiura,

Sorry for the delay in replying to your kind post.

Would you consider page 146 to be the best place to start?

AshleyF

Pages: [1] 2
anything