Jump to content


Photo

bug in v4.2 oct10


  • Please log in to reply
2 replies to this topic

#1 bgreene

bgreene
  • Members
  • 4 posts

Posted 11 October 2007 - 11:19 PM

just installed v4.2
1. following change needed to prevent av when inplaceeditor for a column is changed back to nil
procedure TNxCustomColumn.SetInplaceEdit(const Value: TNxCustomEdit);
begin
if FInplaceEdit <> Value then
begin
// bill greene
if assigned(FInplaceEdit) then RemoveFreeNotification(FInplaceEdit);
FInplaceEdit := Value;
if assigned(FInplaceEdit) then FreeNotification(FInplaceEdit);
end;
end;

2. $define_trial is still defined in nxdbgrid
3. nx_debug is still defined in nxsuite.inc so grid shows remarks at top in claqua
4. try as i might, i cant get the grid to accept keyboard input. i'm using a memory table which
works fine with a normal grid.

#2 Boki (Berg)

Boki (Berg)

    Boki (Berg)

  • Forum Admin
  • PipPipPipPipPip
  • 8,191 posts
  • Gender:Male

Posted 11 October 2007 - 11:53 PM

Hello Bgreene,

1) I have apply your fix. Thank you.

2) $Define Trial is not used and you may ignore it.

3) I have just spot that debug mode is active and re-upload files before 1h, but I will re-upload it now again. In NxSuite.inc simply change string inside {$DEFINE NX_DEBUG}

4) Maybe coEdit flag in Column.Options is set to False? If you can send me small example of code or small project I may see where is a problem. Thank you.

Best regards
boki@bergsoft.net | LinkedIn Profile
--
BergSoft Home Page: www.bergsoft.net
Users Section: users.bergsoft.net
Articles and Tutorials: help.bergsoft.net (Developers Network)
--
BergSoft Facebook page
--
Send us applications made with our components and we will submit them on: www.bergsoft.net/apps.htm. Link to this page will be also set on home page too.

#3 bgreene

bgreene
  • Members
  • 4 posts

Posted 12 October 2007 - 11:39 AM

QUOTE (Boki (Berg) @ Oct 11 2007, 11:53 PM) <{POST_SNAPBACK}>
Hello Bgreene,
4) Maybe coEdit flag in Column.Options is set to False? If you can send me small example of code or small project I may see where is a problem.

That was the problem. I thought editing would be true by default.

Perhaps you could add the following to your grid next release.
if user enters an invalid value eg string in a number field, it generates an invalid value exception. in my case, eurekalog would pick this up and treat it the same as a bug in the program. i can filter out these non-bugs but it would be nice if your grid would trap these invalid data entries, pop up a dialogue and prevent the exception from going further up the line.
Regards bill




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users