PureBasic Forums - English

Studying the code a little, hats off there maestro. That's a novel way of doing things.

Very nice! Awesome job, net'.

Fantastic bit of code, perhaps it should get included in a future update, 4.5 or something.

Thanks for the kind words everyone. As I see it there are three main tasks left:

1) Implement a system of setting/clearing tabstops

2) Implement routines for setting/retrieving the various states of the gadget

3) Implement optional logical measurement units

Task #1 is the next on the list, I'm considering a couple different approaches. Anyone have ideas on a good way to proceed?

Really neat Thank You

Nice code!
Even i never understood the meaning of that in MS Word. (I use Openoffice 2.1)

Very nice code.
These neat little features should be included in a community project like PBOSL.

Update Tuesday April 10: added full tabstop functionality, new code is in the first post. Please try to find bugs, it's appreciated.

We're getting there!

Added more compatibility to the tabstops & sliders, now they draw the indicator lines on creation and upon being clicked. (they used to wait for being moved) Code in first post.

Also, the tabs are lined up to the background a bit better, although if a tab is sitting right on a number it can look a bit ugly, which I imagine can't be helped.

How about delete the iTab.bmp file before ending?

Sorry that was in there just for debugging purposes, I'll take it out now. Thanks for pointing it out!

Excellent.

Noticed that the tabs, whilst being dragged, can move vertically. A bug?

Thanks!

The vertical tab movement isn't a bug, it was intentional so someone could drag the tabs off the bar upwards if they want, but after some reflection and working with it, I don't like it either so I'll probably take it out.

Update:

- The tabs don't drag up anymore

I've never been happy with how hard it was to click an existing tab, with that clipping region applied there were only two pixels width- and height-wise you could click for the tabstop to receive the WM_LBUTTONDOWN message. I initially experimented with different shapes for the tabs with thicker "black parts" but they were ugly. So today I've implemented a small routine in the BaseProc procedure to test if a WM_LBUTTONDOWN it gets is actually inside the full windowrect of an existing tab. If it is, it sends the message on to the tab and doesn't process further. So - just a bit of explanation for the second improvement for this morning, which is:

- It's now much easier to select an existing tabstop!

New update for Wednesday Apr 11, details and code in first post.