NetTalk Central

Author Topic: Browse Filter broken in template ?  (Read 3075 times)

MyBrainIsFull

  • Full Member
  • ***
  • Posts: 134
    • View Profile
Browse Filter broken in template ?
« on: November 02, 2014, 07:44:50 PM »
NT 8-31
on any browse, in the settings - Filter Tab

if I have a filter like Stu:Id = 4
then I delete it,  it generates a bug as the filter is not ignored if it is blank

ie there is no way to turn it off.

I checked with F10 to make sure there was no white space

Kevin



[attachment deleted by admin]

terryd

  • Hero Member
  • *****
  • Posts: 759
    • View Profile
    • Davcomm
    • Email
Re: Browse Filter broken in template ?
« Reply #1 on: November 03, 2014, 01:44:22 AM »
Hi Kevin
Just tried this with the web3 demo app
I put in a trace in the After setView embed point (see below)
  ! Start of "After SetView"
  ! [Priority 5000]
   p_web._trace('loc:FilterWas  = ' & loc:FilterWas)
  ! End of "After SetView"
Compiled and ran the program - result OK debugview value is loc:FilterWas =     All records displayed (which is correct)
Put is a filter in the filter template 'MAI:MailBoxName = a'
Compiled and ran the program - result OK debugview value  is [7352] [st] [netTalk][thread=3] loc:FilterWas  = MAI:MailBoxName = a. No records were displayed (which is correct)
Removed the filter and recompiled and ran - Result OK debugview value is [4396] [st] [netTalk][thread=3] loc:FilterWas  =       All records displayed (which is correct)

Maybe try the above using debugview to display any values which may be in the filter string or maybe use LEN(CLIP(loc:FilterWas)) to see if there is anything hidden
« Last Edit: November 03, 2014, 09:46:17 PM by terryd »
Terry Davidson
Windows 10 64 bit/Windows7 64bit
Clarion 9.1.11529/Clarion10 12567
Nettalk 913
Nettalk 1015
StringTheory267/Winevent515/XFiles298/MessageBox239/Cryptonite186

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: Browse Filter broken in template ?
« Reply #2 on: November 03, 2014, 11:06:13 PM »
Hi Kevin,

>> then I delete it,  it generates a bug as the filter is not ignored if it is blank

I'm not able to duplicate the effect here (and apparently neither was Terry), so either there is something in the filter that you can't see, or maybe your install is a bit screwy.

You can probably work-around the problem by setting the filter to
''
but what you are seeing is not normal behavior.

cheers
Bruce