DSP Robotics Support

For those new to RubyEdit:

I made an example showing the difference between the RubyEdit methods "mouseLUp" and "mouseLUpCaptured". You will see that there is practically no reason to use the former.

Thanks, MyCo, for the reminder!

Yeah, it took me a while till I've discovered this myself... We should make a complete list of things missing in the manual and send it to malc to add them...

When you haven't heard about "mouseLUpCaptured", you might not know that one either:


It is triggered, when the module GUI Size changes.

MyCo wrote:When you haven't heard about "mouseLUpCaptured", you might not know that one either:

Code: Select all

def viewSize(x,y,w,h)
...
end

It is triggered, when the module GUI Size changes.

Thanks a lot! How come that such important and convenient methods are not even mentioned in the manual? I understand that some lesser meaningful methods slip through, but those?

I discovered quite a lot undocumented methods (e.g. setARGB/getARGB for the Color class, caption, parent, etc.), but especially those two hide themselves very well. Even now that I know they exist, I still can't find them.

tulamide wrote:How come that such important and convenient methods are not even mentioned in the manual? I understand that some lesser meaningful methods slip through, but those?

Yeah, I guess it just has been forgotten. Some of them are just not noteworthy though, because they are outdated or useless already "viewSize" is one of them. You don't really need it, because when the GUI size changes, there is always a draw call right after that. You can just use the view argument in the drawcall to get the new size.

The missing documentation is not only related to Ruby code. In fact the most undocumented functions are in the DSP code... Just noticed that a couple of days back. There are at least 6 functions that I used before and they aren't in the documentation... I mean, even the "|" operator isn't in there

MyCo wrote:You don't really need it, because when the GUI size changes, there is always a draw call right after that.

I thought of another use for this. I didn't test it yet, just took your word. But if it is triggered while resizing, it can be used to differentiate between normal redraws and redraws caused by a resizing view. A complex composed view might want to do an alternate drawing with reduced complexity while the view is resized, to reduce processor load.

The missing of proper documentation for dsp most probably didn't catch my attention because I'm already overchallenged with the things that are documented