Discussion of article "Graphical Interfaces X: Time control, List of checkboxes control and table sorting (build 6)" - page 4

 
Anatoli Kazharski:

Reproduced all such cases. This applies to all elements that are used as components in other elements. Detected when the initial absolute coordinates of the form, when creating the GUI, are greater than (1,1).

The fix will be in the next build. As a temporary quick fix, either (1) your examples or (2) just initially set the form in coordinates (1,1) will work. The second one is better, as it may sprinkle in other modes of element positioning.

Well I don't use other positioning modes yet, but the forms open relative to the coordinates of other forms. So I'll leave it the way I did and wait for your update. It will take a long time, though (and there are some very necessary things there, without which it is not convenient now).
 
Need an element that will add arbitrary text to an arbitrary place (as an information marker) that cannot be interacted with, how do you advise to do it?
 
Pavel Kolchin:
We need an element that will add arbitrary text in an arbitrary place (as an information marker), how do you advise to do it?

Perhaps an element like CTextLabel would be suitable ?

Examples can be seen in this article: GUIs X: Text Input Box, Picture Slider and Simple Controls (build 5).

 

Anatoly, your work is grandiose, and I even want to put it into practice, but many things hold me back. In principle, you can modify your code to suit your needs, but it is probably better to create your own code.

For example, such an annoying little thing. The idea of dynamic window resizing has arisen, i.e. many window GUI interfaces allow you to change the window size.

As a rule, the following style, click the mouse in the lower right corner of the window, then the window is pulled to the desired size and the window is scaled.

The first thing I tried was to resize the window.



As a result for TAB1 and TAB2 there is no scalability.


 
Yuriy Zaytsev:

...

Generally the following style has developed, click the mouse in the bottom right corner of the window, then the window is pulled to the desired size and the window is scaled.

There are plans for this, but when it will be I can't say yet.

The thing is that in order to start "conducting" all the controls that are presented in the library, they must first be raised to a certain level. Many of them are now at an intermediate stage, and some of them are just temporary variants.

Yuriy Zaytsev:

...

In principle, you can modify your code to suit your needs, but it's probably better to create your own.

It would be interesting to see your version of the library if you publish it of course.

P.S. Big goals are achieved much faster by joint efforts. )
 
Anatoli Kazharski:

It is in the plans, but when it will be I can't say yet.

The thing is that in order to start "conducting" all the controls that are presented in the library, they must first be raised to a certain level. Many of them are in an intermediate stage right now, and some of them in general, as temporary options.

It would be interesting to see your version of the library, if you publish it of course.

P.S. Big goals are achieved much faster by joint efforts. )

This is if the team works with goals and for results and needs a cool real leader (manager) - not a MANAGER.

 
Yuriy Zaytsev:

This is if the team works with goals and for results and needs a great real leader (manager) - not a MANAGER.

...

You can do it without a manager. If everyone makes, some small contribution to the solution of tasks that have not yet been touched.

If I thought I needed a leader to move things along, this library, at least at this level of development, would still not exist. I realise that this is still far from enough. )

 
Kind regards from Colombia

I want to reiterate my thanks for the work you have done with the graphic interface libraries, they have been magnificent ...

Precisely, on them, I want to ask you a huge favor, which I begin to put in context:

Based on the library updates, I have dared to divide them into several groups, which I will summarize below
Group 1:
Articles 1 to 10-1, delivered is Build 2
it is the "old library" that also has an "old structure"

Group 2:
They are Updates to that Group 1 library, it is still the “old library”, but it has occurred to me to call it an “intermediate structure”
Within this group 2 are Build3 (article 10-2), Build4 (Article 10-3), Build5 (Article 10-4) and Build6 (Articles 10-5)

Group 3:
They are more updates to that "old library" but they have a "new structure"
Within this group 3 are Build7 (Article 10-6), Build8 (Article 10-7), Build9 (Articles 10-8), Build10 (Articles 10-9 and 10-10), Build11 (Articles 10-11), Build12 (Articles 10-12) and Build13 (Articles 10-13)

Group 4
From here, you have updated the core of the library, so I call it the "new library" but with "old structure".
Within this are Build14.1 and 14.2 (Article 10-14) and Build15 (Article 11-15)

Group 5
It is an update to say "New library" but also with "new structure"
Here is Build16 (Article 11-16)

I have done this whole summary because each group supports its own articles except group 2,
when I update to Build5 (Article 10-4) I can't compile articles 10-2, and when I update to Build6 (Articles 10-5), I can't compile articles 10-2, neither 10-3 nor the 10-4

I find it strange that they are not compatible, because there is no talk of a change in structure in that group, (and it does not accommodate group 1 or group 3 either)

Has anyone managed to "adjust" the files so that, at least in that group 2, all articles can be compiled ??
Thank you