Page 3 of 3

Re: Did you know?

Posted: Friday 22nd September 2017 9:25am
by stevedee
In Form view:-
- If you select the width property of a control, the up/down arrows increase/reduce the width.
- If you select the height property of a control, the up/down arrows increase/reduce the height.
- If you select the X property of a control, the up/down arrows move the control right/left.
- If you select the Y property of a control, the up/down arrows move the control down/up.

Re: Did you know?

Posted: Friday 22nd September 2017 2:19pm
by cogier
So it does. Interestng. I knew that using the mouse wheel had that effect.

Re: Did you know?

Posted: Friday 22nd September 2017 2:38pm
by cogier
This does not work with the Cinnamon Desktop as the key stroke is reserved for showing all Virtual Desktops. In the Gambas IDE put the cursor on a line and press [Ctrl]+[Alt]+[Up Arrow]. This will move the whole line up and will jump over other lines. [Ctrl]+[Alt]+[Down Arrow] will move it down. This also works in Writer (for the whole paragraph).

Re: Did you know?

Posted: Wednesday 16th May 2018 1:46pm
by stevedee
Something I don't do very often is set the "tab" order for controls on a Gambas form. Consequently I struggle to remember how its done.

In Visual Basic it was straightforward, you just gave the "TabIndex" property a suitable integer value. If "TabStop" for a control was set to false, then that control would not respond to Tab.

In Gambas it is a little obscure; go to the Properties view, select Hierarchy and move items in the list via up/down arrows so they tab in the required order. The property "NoTabFocus" determines whether or not a control responds to Tab.

Re: Did you know?

Posted: Thursday 17th May 2018 9:43am
by didier18
Hello

Very good idea this "Did you know?" section. initiated by cogier. Thank you.

So, did you know? It is possible to compare values, see which routine is called by which routine and optimize its code. To see the execution time of a command, a routine and even a complete program. This tool can be found in the menu /Debug/Activate profiling.
Once this menu is selected, launch the program to be tested as you would normally do... Then close your program. A window will open (as in the example) and you can view the profiling.
Even louder... It is possible to save the profiles, which allows you to compare the evolution with the different versions of your program.
But of course you already knew...

Have a nice day.