is this a bug?

tab keyword doesn't seem to function properly when used vertically: Rebol [] view layout [ tabs 40 field "Field 1" tab field "Field 2" tab field "Field 3" ] Why doesn't the tab between field 2 and field 3 show up? Also, the last example in section 10.2 in rebol developers guide doesn't seem to demonstrate anything about tabs. tab sizes are specified, but not used.. Here is the example: view layout [ tabs 40 field "Field 1" field "Field 2" field "Field 3" return across tabs 100 button "Button 1" button "Button 2" button "Button 3" ] shouldn't it be: view layout [ tabs 40 field "Field 1" tab field "Field 2" tab field "Field 3" tab return across tabs 100 button "Button 1" tab button "Button 2" tab button "Button 3" tab ] Rishi

Yes it does. If you put a tab before the first field, it will work: view layout [tabs 40 tab field tab field tab field] In your example the first field is not tab aligned, but the second and third are. Anton.

hi Anton. I'm sorry, it still seems like a bug to me. The documentation says: TAB skips forward in the current direction (across or below) to the next tab position. So if you have the following code: rebol [] view layout [ tabs 40 ;sets tab space to 40 pixels. field "Field 1" ;displays field 1 with no tab tab ; tab 40 spaces below field 1 field "Field 2" ;display field 2 tab ;tab 40 spaces below field 2 field "Field 3" ;display field 3 ] But it does not seem to work this way. Instead it seems like there is 80pixels between field 1 and field2 and 40 pixels between field 2 and field 3. It doesn't seem to make sense to me... rishi ] --- Anton <[arolls--bigpond--net--au]> wrote:

Anton has shown how it will work. In your new example you have the comment "tab 40 spaces below field 1" which suggests that you believe a TAB generates space from the current position which is the bit that is confusing for you. Tab does use the current position to calculate the next but not by generating space.. TAB is like a "snap-to-grid" option in a graphics program. That is what "TAB skips forward in the current direction (across or below) to the next tab position." means. The positions are pre-defined. TABS 40 sets up a grid of tab positions. When you use TAB it calculates that next position and places your next element at that point. This is why you must use TAB on your first field if your first field is not already at the correct location. The only thing is that that there is no Tab-zero (unfortunately). VID it goes from Tab-one up. Hope that clear it up! Brett.

Damn that send key is too easy to hit. Just ignore this comment in my last mail.

> The only thing is that that there is no Tab-zero (unfortunately). VID it > goes from Tab-one up.

From: "Brett Handley"

<snip> > TAB is like a "snap-to-grid" option in a graphics program. That is what

> skips forward in the current direction (across or below) to the next tab > position.

<snip>

Rishi, As Brett says, specifying tabs 40 means there are tab positions at 40, 80, 120 etc. Run the following program. If you look at the offset and size of the first field, you will notice that its bottom edge is at 44. Then we add on the default spacing between elements (8) and we get to 52. It has missed the tab at position 40 by 12 pixels. Therefore the next tab will be at 80. rebol [] view layout [ ;space 0 tabs 40 f1: field ; 200x19 tab f2: field tab f3: field do [ print [f1/offset f1/size] print [f2/offset f2/size] print [f3/offset f3/size] ] ] If you reduce the vertical size of f1 to 11, [f1: field 200x11], then it tabs correctly. Greater than 11 jumps over the tab. If you specify spacing of zero, and the vertical size of f1 to 19 (uncomment the comments above), then you will see that the first field just fits in before the second tab position, 40, which is greater than 20+19. I am looking to see if there is a way to set an offset to the tab positions. Anton.

> I am looking to see if there is a way to set > an offset to the tab positions.

Thanks for the replies... Very helpful.. rishi --- Brett Handley <[brett--codeconscious--com]> wrote: