Good Morning, and thanks to both of YOU for the replies.
1 - The ability to set the height of the rows and headings and the text of the headings to be spaced correctly in proportion to the chosen Line Height and chosen Font for the browse.
This needs to be sorted out.
Detlef Hofner very kindly modified WBROWSE.PRG for me about a year ago so that I could pass a parameter oLbx:nLineHeight := nValue and this did work for a time for the most part but it could not space the heading text correctly as apparantely the heading text is drawn by WBRWLINE.C (the heading text would just move down and not center between the horizontal lines of the heading. Changing the font also caused problems when calculating the correct spacing between the horizontal lines of the browse).
I did try and make sense of the changes that he made and attempted to implement these changes into subsequent releases of WBROWSE.PRG but eventually the files became too different and again, for someone with my limited knowledge of the internal workings of FWH, making these changes to the FWH source became more time consuming than I could afford and I was always nervous that I would be messing with some or the other new function or fix that was part of a newer release of WBROWSE.PRG.
For this reason I really think that these changes need to be incorporated as standard BY THE DEVELOPER.
2 - The headings to appear the same as any other XP application that has a data browse (like MS Outlook for example) i.e. underlined when mouse is moved over them just like FiveWin Win32 Headers.
Really needs to be implemented BY THE DEVELOPER.
3 - Correct operation of the vertical scroll bar (been on about this for just as long).
The main problems are as follows:
When adding a new record I have to do some fancy footwork to ensure that the vertical scroll bar stays in synch with the database. The only way that I can do this is by including the following code immediately after adding my new record:
oLbx:GoBottom( )
oLbx:GoTop( )
DBSeek( Key Of Newly Added Record )
oLbx:VSetPos( OrdKeyNo( ) )
oLbx:Refresh( )
Just try to add a record without this code and see what happens. The new record is added and displayed and the vertical scroll bar appears to be in synch but immediately press the Up Arrow key after adding the new record and the scroll bar indicator (I forget what the little block is called) jumps right to the top of the scrollbar and from then on is out of synch with the database until you press End, Ctrl Page Down or Up, Home, etc. etc. which seems to resynch it.
My workaround code (above) results in much jumping around of the scroll bar after adding a new record and this just looks silly and results in every new user that uses something of mine saying 'what happened there when I clicked OK'!
Using my workaround (above) a newly added record is always displayed as the first record at the top of the browse (after all the movement has taken place although this ensures that the scroll bar is back in synch with the database). Your new record should be displayed at the current position of the scroll bar highlight bar i.e. sort of inserted at the current position of the scroll bar highlight.
Another even simpler problem to replicate is to open a browse, press End or Control End (puts you at the last record) and then press Down Arrow. Now move up with the Up Arrow key or Mouse and you will find that now your scrollbar is one record behind the database and remains so until you press End, Control End, etc. etc. The same applies when using the opposites of Home, Control Home, etc. etc.
The only problems with this, that I am aware of, have to do with indexes filters, scopes, and deleted records.
If we have to be constantly aware these conditions and have to constantly make allowances for them when displaying a basic browse of our data then we have problems.
The fact of the matter is that when I display my data using a browse it should display it any way I want it and in order that I want it and the scrollbar should be in synch with the database at any given time.
Sorry - I know that I appear to be coming down really hard on this but the ability to be able to browse databases correclty really is not a 'nice to have' but rather a necessity.
5 - Correct alignment of the vertical lines between fields in relation to their headings (the vertical lines have always been slightly offset to the right since FiveWin 2.2 and does not look very nice).
Actually, this is a optical illusion. If you do a screen capture and enlarge it you will see that the line is right between the columns. The problem is that there is a black shadow drawn on the left and bottom sides of the previous column header (to make it 3d). The vertical black line on the previous header makes it seem that the vertical line between the columns is in the wrong place. However, I never even noticed this until you mentioned it, so I doubt many of your users have.
It has been noticed on more than one occasion believe it or not.
I am going to try experimenting with the line styles so maybe this is not an issue.
Regards,
Dale.