yes but it not is the same please see https://material.io/design/components/text-fields.html#anatomy at bottom search "icons" 1. Icon signifier Icon signifiers can describe the type of input a text field requires, and be touch targets for nested components. For example, a calendar icon may...
do you have insert also the possibility to insert icons to validate the get ? 1. Icon signifier 2. Valid or error icon 3. Clear icon 4. Voice input icon 5. Dropdown icon sample : http://www.devcomponents.com/dotnetbar/img/SuperValidator17.png http://www.devcomponents.com/...
Added new clauses and datas, methods in TGET [ <infield: INFIELD> Clause initial for active others clauses [INCAPTION <cInCaption>] Text for infield box When DYNAMIC clause is active, not need this clause, cInCaption is replaced with cCuebanner [INRECT <aInRect>]; aRect for paint: ...
Dear Otto, There is no need to create a new control. We can simply use standard GETs: #include "FiveWin.ch"function Main() local oWnd, cName := Space( 20 ), oGetName DEFINE WINDOW oWnd COLOR "N/W*" @ 10, 10 GET oGetName VAR cName OF oWnd NOBORDER COLOR &quo...
Dear Antonio, please go ahead and design a control. Look at this: https://material.io/design/components/text-fields.html#anatomy https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1Bna_M1j7fpIpDbNOLR1d32fjB7kARjLE%2Ftextfields-anatomy-label-text-do.mp4 https://storage.goog...
Dear Antonio, thank you so much. Now I will check if the hypotheses that “Infield Top Aligned Form Labels“ are making scanning a DIALOG easier. There are also opposite – as allways – views: http://forums.fivetechsupport.com/posting.php?mode=reply&f=3&t=36283 Although ...
Dear Otto, There is no need to create a new control. We can simply use standard GETs: #include "FiveWin.ch"function Main() local oWnd, cName := Space( 20 ), oGetName DEFINE WINDOW oWnd COLOR "N/W*" @ 10, 10 GET oGetName VAR cName OF oWnd NOBORDER COLOR "...