ofxOscSenderExample needs text polish

[damian0815]

the text printed on screen is inaccurate and a bit misleading:

    buf = "sending osc messages to" + string(HOST) + ofToString(PORT);
    ofDrawBitmapString(buf, 10, 20);
    ofDrawBitmapString("move the mouse to send osc message [/mouse/position <x> <y>]", 10, 50);
    ofDrawBitmapString("click to send osc message [/mouse/button <button> <\"up\"|\"down\">]", 10, 65);
    ofDrawBitmapString("press A to send osc message [/test 1 3.5 hello <time>]", 10, 80);

• no spaces between host and port string
• <button> isn't sent on click

[bilderbuchi]

thanks for the report, Damian!

[tpltnt]

I can reproduce the bug as of b5db2cc. I ran the ofxOscSenderExample and used wireshark to check. The filter to check for the mouse messages is osc && udp.port eq 12345 && osc.message.string. I also get

[ error ] ofImage: loadImage(): couldn't load image from ofBuffer, unable to guess image format from memory
[ error ] ofImage: loadImage(): couldn't load image from ofBuffer
ofApp:: sending image with size: 0

I do see a mouse button down message though.

[tpltnt]

I tested with an external USB mouse. When i click left button, i get a "mouse down" for button 0. When i click with the right button, i get a "mouse down" for button 2. When i click with the scroll wheel, i get a "mouse down" for button 1. After clicking the scroll wheel, i only get "mouse up" messages, but no "mouse down" anymore. When i use the mouse(pad) on my computer, i can sort-of deterministically (but inconsistently) switching between "mouse up" and "mouse down" messages by clicking the middle button (button 1). I am seriously confused now.

[tpltnt]

The host string issue is fixed now. The clicking issue confuses me. If anyone wants to pick up where i left off, check my local branch.

[ShadowMitia]

I tried to reproduce the bug but couldn't. Maybe this issue has been fixed since then? Or it was just a driver issue?

[arturoc]

thanks!