NetTalk Central

Author Topic: Close button changes to Save Button on Form with Browse Procedures  (Read 8109 times)

AZIS350

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
    • Email
On a form that contains a browse control, in View mode the 'Close' button on the form changes to a 'Save' button (and process) when you tap on a browse item (to view the form of that browse record) and then 'Close' out of that browse form. You are returned correctly back to the original form, however the 'Close' button on the original form (which is still correctly in View mode) is now displayed as 'Save' and will not exit out of the form. Any ideas? NT 6.12 (I'm in Mobile mode, have not tested it in standard browser mode).

Second question (also while in Mobile mode) is when displaying a Browse with a Locator (I'm using the Contains option), if you type a value in the Locator and tap Done (or return), it does not perform a locate function (nothing happens). Only if you tap on the browse heading to re-sort the column and then re-enter the locator value does it then work. Looks like the focus upon first entering a browse is not on the Locate field? No special logic being used - standard browse w/ locate function.

Last question is does anyone know how to identify a button icon (jquery mobile) to be placed on a form? Example: Using a button to call Googlemaps (logic works fine), but the button is a small round button with no text.  I'm using the Button tab of the form's Field Property, but not sure what parameters to enter to have a jquery mobile style button (i.e. like Close or Save but with changed text to say 'Map'). Any help would be appreciated.

Thanks.
Bob Zimmerlich


Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #1 on: December 29, 2011, 02:10:59 AM »
1. Please test in Desktop mode and let me know if it's the same.

2. Does your browse have a default column set? If not then set one of the columns to be the initial sort order.

3. I've added options in 6.13 so you can specify the mobile text (defaults to desktop text) and also the mobile icon.

AZIS350

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
    • Email
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #2 on: December 29, 2011, 07:41:05 AM »
Thanks Bruce. I've tested the following:

1. In desktop mode, same thing occurs ('Close' button on form changes to 'Save' after clicking on an embedded browse record and 'Close' out of that browse record back to main form). I don't have any embedded custom logic - just a standard form procedure with included browses on the form. All are only View mode only (only View is checked as valid action) and using a Button for View selection next to each record in the browse (rather than having a View button to click on).

2. I do have the locator column set as the default sort (sort default checkbox is checked). I tested this in Desktop mode and there is no problem with the Locator being focused. However, in Mobile mode when you first display the list and enter a value and then tap on Done or Return nothing happens. But if you re-sort the column first and then enter a value and tap on Done/Return (on the pop-up keyboard on the iphone) then it works perfectly. So it appears to be related to Mobile mode.

3. Excellent :)

One other small item I'm noticing. I'm using Mobile menu style with a Top Menu level and a series of '1' submenus below it (i.e. Top menu = Customers, submenus = 'Search By Name', 'Searcy By Account', etc.). When the submenu calls a browse, and then you click on 'Close' to return to that level 1 submenu that called it, there is an error that pops up in the middle of the page  (light yellow background around the error) for a few seconds that says 'Error Loading Page'.  Not sure where that is coming from. Do I need to set a return procedure or URL perhaps?

Otherwise, the mobile features in NetTalk6 are working great for us.

I'll continue testing on my end with some additional settings, but any other info you may have would be appreciated.


AZIS350

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
    • Email
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #3 on: January 02, 2012, 07:56:23 AM »
Thank you for 6.13 :) It fixed the issue with returning to mobile menu from a form (it used to error out with 'Error loading Page' but now works as it should) and the mobile button and text inclusion works perfectly.

The focus on locator column still remains as an issue (#2 in original post), as does the 'Close' button of a form changing to 'Save' when in view mode and viewing a record from a browse included in the form (#1). Any workarounds you can think of, or has anyone experienced this in mobile mode and knows why? Thanks.
« Last Edit: January 02, 2012, 12:01:56 PM by AZIS350 »

AZIS350

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
    • Email
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #4 on: January 06, 2012, 09:59:00 AM »
Sorry to bump this, but not sure if anyone else has experienced the same problem with locator not being focused in mobile mode. User has to first tap on a column heading to initiate a sort, and then the locate field has focus. Column is checked as default sort and works well when in non-mobile mode. Thanks.

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #5 on: January 06, 2012, 10:18:36 AM »
thanks for the bump - more info coming soon...

AZIS350

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
    • Email
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #6 on: January 24, 2012, 09:22:08 AM »
Any additional information on the locator problem in mobile mode? Everything else in our app works great and we're ready to release it to our clients, but since this is a major issue we can not release it until it either has been corrected or there is a work-around we can program. I believe a few other posts here reported a similar problem. Thanks Bruce.

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #7 on: January 25, 2012, 03:13:45 AM »
I know it doesn't always seem like it, but I am grateful for the bump. With so many things happening it's easy for some to slip through the cracks. So thanks again for that.

The issue should be sorted in the 6.17 build.

cheers
Bruce

AZIS350

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
    • Email
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #8 on: January 25, 2012, 10:17:46 AM »
Thank you Bruce. I would rarely bump an item unless it was really important to my bottom line :) Thanks for your understanding, and finding a solution. Much appreciated.

AZIS350

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
    • Email
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #9 on: January 26, 2012, 07:11:30 AM »
Unfortunately 6.17 didn't seem to correct the locate problem while in Mobile mode. Enter the locate value (I"m using Contains, but have tried it with position as well and doesn't work either) and tap the Return or Done button on the mobile device and nothing happens (you can tell no search is going out, no wireless activity, etc.). But, just tap on a column heading to sort the column, then enter the value again into the Locate field and when you tap Return or Done it immediately does the correct Locate.

Just as a side note, the other issue regarding 'Close' button being changed to 'Save' on the parent form after you view a record from a child browse on that form is still an issue as well.

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #10 on: January 27, 2012, 02:14:34 AM »
>> Enter the locate value (I"m using Contains, but have tried it with position as well and doesn't work either) and tap the Return or Done button on the mobile device and nothing happens

I'm unable to duplicate your issue.

I'm testing here on a pretty much "out the box" example nuber 2.
I go to the mailboxes browse, and select a column to sort by (eg name) so the locator field appears.

I then type something into the the locator and click on either "done" or 'return".
In both cases I see a request appear in the web server, and after a brief delay the browse goes to the right position.

I'm using an iPod via wifi for the test.

Earlier I tested with a desktop browser, in "mobile mode", and it also works there, but there you don't have the "Enter" and "Done" keyboard buttons - hence the test on an actual mobile device.

cheers
Bruce

AZIS350

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
    • Email
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #11 on: January 27, 2012, 07:16:44 AM »
I will test further on my end with example 2 and some additional apps and see what I can come up with as a possible cause. Thanks Bruce.

AZIS350

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
    • Email
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #12 on: January 31, 2012, 09:40:21 AM »
Interesting. I tested NetTalk Example 2 in mobile mode, and the locator does not work for us in that application either. I have updated the web folder to make sure it is in current 6.17 version. When using the locator in example 2, it actually does find the locator value even after tapping on the column heading to resort (in my application, tapping on the column heading then allows the locator to work).

Has anyone else been successful in using the Locator in a mobile environment (we are testing with the iPhone)?

Bruce, in my case I do not require the user to select a column first to browse on before using the locate. In our app, the main column is set as the default sort column (since 90% of the time the user will always locate a record based upon that particular column) so therefore when the browse comes up the Locate value is already set to be entered for the default column. If a value is entered and DONE is tapped on the iphone, nothing happens. But if they first tap on the column heading, and THEN enter a locate value then when DONE is tapped it works. But in Example 2, I couldn't even get the locate to work even when a column heading is tapped. Not sure why, any further ideas? Thanks.

AZIS350

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
    • Email
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #13 on: February 02, 2012, 01:41:41 PM »
Bruce, I found the solution to the Locator problem in mobile mode. Not sure if this is something which may be addressed in a future maintenance release, but the following works.

You need to fill in the 'Default Sort Order' in the 'Locators' tab of the browse procedure, even though it states not to use this area if you already have a column selected as a default (which I did). Even though the Locator is based upon a column already specified in the browse list, the Default Sort Order list in this tab must also be defined. Once you do that, then in mobile mode the focus is immediately on the Locate field to do a search without first having to tap on a column before using the locate. Works great, but I'm not sure if that was the intention to use this field for a simple locate on a column already defined.

The only remaining issue now that I have for my particular application in mobile mode is the 'Close' button of a form being changed to a 'Save' button when you view a child browse record on that form and return to the form.

AZIS350

  • Jr. Member
  • **
  • Posts: 62
    • View Profile
    • Email
Re: Close button changes to Save Button on Form with Browse Procedures
« Reply #14 on: February 06, 2012, 09:58:48 PM »
I thought I had found a solution, but unfortunately no.

I've been working with Example 49 (Locators), in Clarion 8 and 6.18. In that example, the Locator works once you have selected a Locator Position, etc (which I believe because it has a Reset process included, resets the browse on that Form and that then allows the Locator to work).  However, if you do not select any checkbox/radio button that form first (I embedded code to set the values to 1) and enter a value in the Locator field, it does not find the value UNTIL you perform some function on the form or browse first - then it works. This is the same problem I have been experiencing in my app as well - only in Mobile mode.

So this is what I have surmised so far.... I can not have a standard Browse procedure (not embedded in a form, but a stand-alone browse) with a Locate field and have it locate the correct record once you initially get into that browse screen. You have to tap on a column heading to sort first, then the locate works perfectly each time. But not the first time into that browse. If you place the browse on a form, the only way it works is if you have a field on the form that you tap first (i.e. Example 49 with the Locate positions, etc. values) and then you can enter a Locate value and it will find the record when you tap on Done or the Search button. But if you do not tap on a field first on that form, same problem - no locate is performed when you tap on Done.

I know  Bruce you mentioned you couldn't replicate the problem on your end, but if you work with Example 49 as is but embed the values needed for the Locate field to be displayed, try on an iPhone to go straight to that Locate field (do not press any other buttons or fields on that form first), enter a Locate value such as 'Cheryl' and then tap on the DONE button of the phone (or even the search icon). Does your record then get located right away or does it just stay on the first record as it does for us? Then tap on the name column header to sort the column and enter the value in the Locator field and then DONE works. Anyone else able to replicate this problem in mobile mode as described with Example 49?