NetTalk Central

Author Topic: URGENT! Buttons stay disabled in browse after popup.  (Read 3518 times)

webwilcox

  • Newbie
  • *
  • Posts: 31
    • View Profile
    • Email
URGENT! Buttons stay disabled in browse after popup.
« on: July 17, 2014, 12:13:14 PM »
I'm using clarion 9 and Nettalk 7.  I have a browse with a button that calls a form as a popup.  The form works fine and saves appropriately.  However, after the same is done and the browser returns to the browse list, all the buttons are still disabled.  The user has to refresh the screen to get the buttons to work again.

I'm planning on putting this app in production in the next day or two but can't seem to get this problem fixed.

Stu

  • Hero Member
  • *****
  • Posts: 510
    • View Profile
    • Email
Re: URGENT! Buttons stay disabled in browse after popup.
« Reply #1 on: July 17, 2014, 02:32:18 PM »
I'm actually having this issue since upgrading from 7 to 8.

Used to have it long ago in 7, but since was fixed for whatever situations I had.

Are you using the latest 7 version?
Cheers,

Stu Andrews

webwilcox

  • Newbie
  • *
  • Posts: 31
    • View Profile
    • Email
Re: URGENT! Buttons stay disabled in browse after popup.
« Reply #2 on: July 17, 2014, 05:41:01 PM »
I'm not on the latest version.  I went to install it and found out that I needed to install the latest string theory as well.  However, the capesoft website seemed to be down so I couldn't get to it.  I'll update both tomorrow and see if it fixes it.

Stu

  • Hero Member
  • *****
  • Posts: 510
    • View Profile
    • Email
Re: URGENT! Buttons stay disabled in browse after popup.
« Reply #3 on: July 17, 2014, 05:50:07 PM »
Okay, so I've just discovered why it was happening for me.

In NT7, in browses, for local vars, you could leave the picture blank.

In NT8, if blank, it automatically assigned the string picture.

A lot of my local vars are XHTML-ified.

@s255 is NOT GOOD for big html strings, obviously :)

So this was fixed for me after going through my browse fields and putting a blank string instead of @s255 for the picture!
Cheers,

Stu Andrews