Libraries: EasyAndFastGUI library for creating graphical interfaces - page 10

New comment
 
Anatoli Kazharski:

Yes, there is such a restriction now (left margin only).

Thanks , it would have taken me another day )) .

 

In MT4 version SimpleButton lack function to change the button text/caption .


SimpleButton.mqh

   string            Text(void)                        const { return(m_button.Description()); }
   void             Text(string text)                         { m_button.Description(text); return; }

Add second line in order to get that functionality. Posted here hope helps someone who needs.

 

Question about moving elements.

m_label.CanvasPointer().YGap(newgap);
m_label.YGap(newgap);
m_label.Moving();

In what cases it may be necessary to move separately the canvas, separately the element itself?

 
Oleksii Chepurnyi:

A question on moving elements around.

In what cases it may be necessary to move separately the canvas, separately the element itself?

I don't understand the question.

 
Anatoli Kazharski:

I don't understand the question.

We specify the new distance separately to the canvas and separately to the element itself. It would be logical to just specify the distance to the element and move it together with the canvas.

That's what I'm asking, what's the point of separating? :)

 
Oleksii Chepurnyi:

We specify the new distance separately to the canvas and separately to the element itself. It would be logical to just specify the distance to the element and move it together with the canvas.

That's what I'm asking, what's the point of separating? :)

What are you trying to do? What is the task? To programmatically move a form with elements on the chart?

 
No, the element in the mould. Let's say to remove the label below.
 
Oleksii Chepurnyi:
No, the element in the mould. Let's say you rip off the label below.

These are two different objects. One is part of the other. There are more complex composite elements and each part needs to be given relative coordinates. Relative to the main element of which they are a part.

You can add a virtual method to the base class of the element, which will make it easier to move elements at runtime.

Try this.

 
Anatoli Kazharski:

They are two different objects. One is a part of the other. There are more complex building blocks and each part needs to be given relative coordinates. Relative to the main element of which they are a part.

You can add a virtual method to the base class of the element, which will simplify the movement of elements during the execution of the programme.

Try this.

The components of complex elements are bound to the main element and move together with it. As far as I understand... And the canvas somehow fell out of this concept :)

The purpose of this question was to find out if there are cases when you need to move an element without canvas or canvas without element?

I have an idea to add something like this to CElement::Moving

   m_canvas.XGap(m_x_gap);
   m_canvas.YGap(m_y_gap);

So that the canvas always moves behind the element.

Nothing will break in this case? :)

 
Oleksii Chepurnyi:

The components of complex elements are attached to the main element and move together with it. As far as I understand... And the canvas somehow fell out of this concept :)

The purpose of this question was to find out if there are cases when you need to move an element without canvas or canvas without element?

I have an idea to add something like this to CElement::Moving

So that the canvas always moves after the element.

Nothing will break in this case? :)

Initially there was no such task that after creating GUI it was necessary to move elements. Everything was based on the idea, when in each element all the necessary behaviour was already implemented.

Counter questions: Why do you need to move elements? What do you want to do? What behaviour when interacting with the GUI do you want to get?

To understand if something will break, you need to test all elements after each change in base classes. It's already hard to say that right away. It's been a while since I've looked deep.

Create a test GUI with all elements of the library and test them after changes.

1...34567891011121314151617...45
New comment