I had some bad news this morning. I received an email from rfb that read, “We have found a way to fix your error”. Now, in the past few months, I have been receiving so many messages from rfb that it is difficult to even remember which ones are “related” to the one that was sent. Today I found out that the email was actually about a bug in my desktop widget.
The rfb protocol is a standard for getting information from rfb clients to rfb servers. It’s been around since 1996 and it’s one of the most important pieces of rfb’s networking stack. The protocol works by sending data back and forth between rfb and rfb clients. We have to send rfb an email at least once to be able to receive the data. If we don’t send it, we won’t see the data.
The rfb protocol error:bad desktop size 0x0 is a common one and it is caused by the fact that rfb clients only accept rfb servers that are at the same size as their widget. An rfb client that is larger than its widget will not be able to receive the data.
rfb protocol error:bad desktop size 0x0 is an easy one to fix. You can either resize your rfb client to the size of your widget or you can use one of the many rfbs client sizes that work on all rfb client types.
I tried both, and the first one was far better. I found it easier to resize and not have the rfb client take up so much of my desktop. I also found it easier to see the data because I had less windows open, and I was able to see that I had a rfb client that was a little larger than the widget size.
With the widget size, the data is very hard to see. You can’t really see the size because it’s too small. But with the rfbs client size, you can see the data because it’s much larger.
When I wrote the code, I included the rfbs client in the header, but I am not sure I could get rid of it without destroying it.
If you put a rfbs client inside the header file of your desktop widget, it will appear much larger than it actually is. You will have to resize it yourself. It should be really easy to remove the rfbs client if you find that it is causing problems.
rfb is a protocol that allows you to send data between your desktop widgets and other applications in the same window. In the case of the rfbs client, this protocol allows the widget to send you stuff about the widget itself and the data that the widget sends back to you. These two things are referred to as the “protocol” and “content”. The protocol is very simple. There is a data type called “desktop”.
The rfbs protocol is an application so it runs in the same window as your applications. The protocol allows you to send and receive data between windowed apps. If you don’t set up your application to be the client for the rfbs protocol, you will not be able to communicate between your applications using rfbs.