get_double() asserting on valid input about socket.io-client-cpp HOT 8 CLOSED

Can you paste some piece of code?

from socket.io-client-cpp.

On the node server side I am sending in

maoSocket.emit 'play', {file: "#{__dirname}/8sec.mp3", offset: 5.0}

Then on the receiving end

        h.socket()->on("play", socket::event_listener([&](event& event){
            message::ptr const& m = event.get_message();
            map<string, message::ptr> eventObject;
            String filename;
            double offset = -1;
            if (m->get_map().find("file") != m->get_map().end())
                filename = m->get_map()["file"]->get_string();
            if (m->get_map().find("offset") != m->get_map().end())
                offset = m->get_map()["offset"]->get_double(); // <- Asserts here unless I use get_int()
            if (m->get_map().find("event") != m->get_map().end())
                eventObject = m->get_map()["event"]->get_map();
            playFile(filename, eventObject, offset);
        }));

Thanks!

from socket.io-client-cpp.

Can you look at the actual transmitting json，I think it converted 5.0 to 5. So offset was interpreted as integer by client.

from socket.io-client-cpp.

You have had a common case. I'll think about providing generic accessors for number types.

from socket.io-client-cpp.

Thanks, I'm pretty sure the conversion from 5.0 to 5 is the culprit. But since all javascript numbers are doubles wouldn't it make sense to make get_double() always be valid on numerical values? Otherwise, we'd have to add a fractional like 0.00001 to any n.0 value before sending it in and then subtract it out on the client side. Thanks again.

from socket.io-client-cpp.

@oh3netid Yes, your're right.

from socket.io-client-cpp.

try tag 1.5.0

from socket.io-client-cpp.

Works great! Thank you.

from socket.io-client-cpp.