PureBasic Forums - English

Sorry, but I have no idea what you are talking about?

You seem to be messing with the EsGRID source. If that is so, then, well, you are on your own.

If EsGRID is crashing within one of your programs then you have to either send me the code or give me instructions on how to reproduce the crash. What you have posted is of little help.

Sorry Srod, my english is (very) limited.

I didn't modify EsGRID source, I only put a debug line in egrid_listiconcallback() procedure to know why/where my code fails.

My old code (PB 4.30/EsGRID 1.3.2) works fine :roll:

Now I updated to PB 4.40b3/EsGRID 1.4.0) and I was gettin invalid memory errors.

But, I know now my error! The problem was in PureLVSORT lib; Since I had problems with thread safe mode, I disabled it in my code... and it was my fail. Now, All is fine.

So, thank you again for this lib, and sorry for my stupid question

PS:I can send you my code, but I think you will turn crazy if you read it

Hey, a crazy man can not get much crazier!

No problems. Must admit that it didn't look like being an EsGRID problem in this case.

23rd December 2009 EsGRID 2.0.0 for PB 4.4.

EsGRID 2.0.0 is a major update to the EsGRID control in preparation for the new ExGRID control.

Lots of minor bugs fixed (+ one long long outstanding bug whose fix has eluded me... until now!)

Changes.

• New celltype added : #egrid_StaticLink. These text based cells can be used to show hyperlinks and the like as the mouse cursor will change whenever the mouse hovers over them (and the text colour can change). These cells do not show a hightlighting border when selected.
  
  One of the ExGRID advanced demos will show these cells in action (or the ExGRID equivalent of these cells).
  
  Cells of type #egrid_String and #egrid_StaticString can now show 'links' (similar to the #egrid_StaticLink cells mentioned above).
  
  The above two changes have resulted in two new fields being added to the cellinfo structure : IsLink and LinkColour.
• Added a new Cellcallback message : #egrid_RightButtonDown (only fires when the mouse is over a cell). Use #egrid_ContextMenu for the equivalent mouse up message.
• Header cells can now be rendered horizontally, 90 degrees vertically or 270 degrees vertically. Use the new constants #egrid_Esc0 (horizontal) or #egrid_Esc90 or #egrid_Esc270 as appropriate for the param field of the #egrid_FormatCell message. See EsGRID demo 2 for an example.
• Header cells can now be gradient filled.
• The various mouse messages (e.g. #egrid_LeftButtonDown) now only fire when the cursor is over a cell and not when over an unused part of the client area. The exception is #egrid_ContextMenu which will fire regardless (see the user manual).
• When editing cells of type #egrid_String, the edit control will always be left justified regardless of the justification employed within the underlying cell.
• Cells of type #egrid_Combo will now always use the owner drawn combo controls when editing the cell.
• Fixed a long outstanding problem (not really a bug as such). Basically, if you chose a row height 'very close' to the 'font height' in use then it was possible to see corruption within cell borders and the like. This was caused by the caret in the edit control used to edit the cell spilling past the boundaries of the edit control itself.
  
  This has been addressed/fixed by automatically adjusting the font used by the edit control. Now, where you would previously see possible corruption of the cell borders etc. you will instead see the font being used reducing in height (but only in cases where the corruption may have occurred). This seems to be the way other grid controls approach this problem.

More on the new ExGRID control in a separate post.

27th Jan 2010.

EsGRID 2.0.1 (and ExGRID 1.0 beta 2) is a bug fix release.

Bugs with vertical header text have been fixed and an incompatibility between cell tooltips and Windows 7 has been rectified (thanks to DoubleDutch).

You forgot to mention that I haven't had any problems with the (new updated version) and Win9x...

DoubleDutch wrote:You forgot to mention that I haven't had any problems with the (new updated version) and Win9x...

Ah, now I didn't know that! If you are saying that these fixes solve the Win 9x issue as well then that is indeed a bonus? I was kind of hoping that it would, but couldn't be sure!

I'll do some more tests. But imho there are no problems - I've tried it on VirtualPC on Win 7 running Win98 and WinMe - not tried on Win95. The demo I tried was the one with vertical text.

srod wrote: Cells of type #egrid_Combo will now always use the owner drawn combo controls when editing the cell.

I don't like this behaviour (it destroys the layout of one of my applications and i personally think it looks ugly), so i removed the hardcoded line in the source.
Is there any good reason you changed this?
Will there now exist some unexpected behaviour?

Whilst working on ExGRID I took the decision to do this.

There is a rendering problem on Vista (and presumably Win 7) with the original combo type cells which is to do with the way Vista renders themed combobox controls via a timer. You can see this on Vista with EsGRID demo 2 (if you reinstate the original comboboxes). Run the demo (enable XP themes) and choose two of the combo type cells and fill them with different text (one 'Male', one 'Female') and then select the two different cells individually, one after the other, continuously. On vista, you will see a delayed rendering with one cell effectively superimposed on top of the other - albeit very briefly. Yes I could fix this, but only with a quite drastic alteration to the way EsGRID uses combobox controls - something I do not wish to do at this stage.

As more and more people use Vista / Win 7 these days, it just made sense to remove the entire issue by forcing the use of the ownerdrawn combos instead. Personally, I prefer the ownerdrawn ones; although personal tastes must really take a backseat in the light of the fact that the many people running Vista/Win 7 will not appreciate seeing the aforementioned rendering problems if we choose to use the original combos.

Your choice.

Well o.k., this makes things a little clearer then, thanks!

I started Win7 to see the effect you are talking about and o.k., this looks strange.
Then i played with esgrid code and found out, if i disable the #CBS_OWNERDRAWFIXED Style anything goes smooth and my layout isn't destroyed any longer.
From my understanding this Flag should be only for keeping the height of the items fixed, so why does it also hide the grey box on the left of each item (which is the reason for the layout destroying)?

Grey box.... ?

What grey box? Sorry, you've lost me. If you are seeing a gray box on the left of each item then there is something wrong... can you send me a screenshot please?

**EDIT : if by grey box you mean the vertical strip that EsGRID paints to the left of each item, then yes that should always appear with the owner-drawn combo cells. Removing the #CBS_OWNERDRAWFIXED style will destroy that 'border' and will probably destroy a few other things as well!

If you are using an unmodified version of EsGRID and this grey border does not appear then something is wrong. Otherwise I would suspect that some modification you have made has resulted in whatever problem you are seeing. Certainly no one else has mentioned a problem with these grey borders.

Well o.k., box is maybe the wrong name, but a screenshot should explain better, what i mean:

Please see my post above.

That screenshot looks fine - that is how it is supposed to look.

>>Certainly no one else has mentioned a problem with these grey borders.
No real problem, just a layout-problem.

But o.k. i see i have to live with it...

Thanks for the information.