FiveTech Support Forums

FiveWin / Harbour / xBase community
Board index FiveWin for CA-Clipper Adding/Removing tabstop
Posts: 21
Joined: Wed Nov 23, 2005 12:24 AM
Adding/Removing tabstop
Posted: Tue May 16, 2006 05:43 PM

I was wondering if there was a way to add or remove the WS_TABSTOP from a get on a dialog ? The dialog is from an RC file and could also be from a dll file

Posts: 9020
Joined: Thu Oct 06, 2005 08:17 PM
Re: Adding/Removing tabstop
Posted: Tue May 16, 2006 05:55 PM

Can't you just disable the control you don't want to have tabstop?

EMG

Posts: 21
Joined: Wed Nov 23, 2005 12:24 AM
Adding/Removing tabstop
Posted: Wed May 17, 2006 11:53 AM

Disabling isn't going to work in the situation.

because sometimes control 100 ( for example ) will be a say, and sometimes it will be a get and control 200 etc

so rathert than having duplicates of each control in the rc I have everything working except for removing the tabstop when its a say, or conversely adding a tabstop when its a get.

Posts: 9020
Joined: Thu Oct 06, 2005 08:17 PM
Adding/Removing tabstop
Posted: Wed May 17, 2006 11:57 AM

SAYs can't have tabstop, as far as I know. What am I missing?

EMG

Posts: 21
Joined: Wed Nov 23, 2005 12:24 AM
Adding/Removing tabstop
Posted: Fri May 19, 2006 05:54 AM

You're right ... but you can use the same edit text box control in an rc or dll file, for a get or a say, with the read only property. when it's redefined as a "Say" , i have to set the colors to look like a normal "say". the only problem is the tab stop. I would like to remove it when i use the text box control as a "say" , or conversely add it when its used as a get.

Posts: 9020
Joined: Thu Oct 06, 2005 08:17 PM
Adding/Removing tabstop
Posted: Fri May 19, 2006 07:01 AM

You can disable the GET and change its default disabled-color (oGet:lDisColors) to CLR_BLACK.

EMG

Posts: 4840
Joined: Fri Nov 18, 2005 04:52 PM
Adding/Removing tabstop
Posted: Sat May 20, 2006 05:15 PM

Why not just use a normal disabled GET? This is variable data that you are displaying--either editable or not. If you display non-editable data in a disabled GET (with the disabled colors) then everyone knows what it is. This is standard behavior. If you deviate from the standard then you confuse people.

FWH 18.05/xHarbour 1.2.3/BCC7/Windows 10
Posts: 21
Joined: Wed Nov 23, 2005 12:24 AM
Adding/Removing tabstop
Posted: Fri Jun 09, 2006 09:34 PM

That's kinda what I did in the end .. except I didn't want the disable look but i did use the button colour as the background colour for the get. I had to hide some as well. THanks for all suggestions

Continue the discussion