Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: Official RIVA thread
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
Which client are you referring to? I was talking about the C++ one, which is installed by our installer. The target port and address ends up just getting spit out on the command line of the client, so you can modify it there, though it'll go back the next time you run the installer if you don't change it during the install.

The C++ one I wrote so I know it's not doing the simple mode. It has the ability to do the simple mode, via a command line switch, just for testing. But otherwise it does the full protocol.
So, one obvious thing that's different is that, you move the mouse before you click. Then, on the subsequent click, you probably haven't moved it much. Are you guys doing the appropriate throttling of mouse move messages? Just as another sanity check, move to the button, click it, click it again to make sure it worked, then move the mouse rapidly a bit within the wndow and then come back and click the same button it again. Does it fail again or work?
These are touch-screen devices. No mouse.
Dean Roddey Wrote:Which client are you referring to? I was talking about the C++ one, which is installed by our installer.
Yes, that's the one.

Quote:The target port and address ends up just getting spit out on the command line of the client, so you can modify it there
So what would be the command line parameters to use at the CQC prompt to start it on the different server? Or do I have to reinstall to select a different one?

Quote:It has the ability to do the simple mode, via a command line switch
And you're sure the switch hasn't been stuck in that mode for a while? Wink
Fonceur Wrote:So what would be the command line parameters to use at the CQC prompt to start it on the different server? Or do I have to reinstall to select a different one?

Yeh, just look at what's there in the start menu and start it up that way in the command prompt.
This is getting funny... Wink With 2 buttons:

- First click of button one = nothing.
- Second click of button one = press effect.
- First click of button two = nothing.

- First click of button one = nothing.
- Move during that click, releasing outside = nothing.
- Second click of button one = nothing!

- First click of button one = nothing.
- Move during that click, releasing on button 2 = nothing.
- First click of button two = press effect!
Dean Roddey Wrote:Yeh, just look at what's there in the start menu and start it up that way in the command prompt.
OK, I wasn't looking at the start menu options, found it now. So connecting to batwater's RIVA server with the C++ RIVA client, I do see the alpha blit of the individual image, which confirms it's the real protocol. By clicking and moving the mouse outside the area, I do see the RIVA server sending the alpha blit to update the image, which it isn't doing for the taRIVA client... And yes I only send the MOVE command every 350ms or so.

I've attached the test template.
Do you update the position as well when you send the click, to make sure that you are sending the current position when the click occurs? Otherwise, the last position might have been outside of the button last time you updated it.
Yes it's sending the current position at that 350ms (or so) mark.
Fonceur Wrote:Yes it's sending the current position at that 350ms (or so) mark.

But you also send the position in the press event. Are you getting the most recent position when you send the press event? If you are just sending the most recent position stored that long ago, it might be outside of the button.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39