NetTalk Central
NetTalk Web Server => Web Server - Ask For Help => Topic started by: astahl on July 02, 2013, 09:27:14 AM
-
Hi All,
I have a second page loaded browse below the main browse and it should have a hundred or so records to show 10 at a time.
It shows the 10 but I no longer have the navigation buttons for that browse in version 7.13.
Ashley Stahl
-
Hi,
I concur, my app now does not show navigation buttons when more records are available when refreshed from the form containing the browse. I can duplicate this problem with my VIEW01 example (See Attached). Note that this app's browses worked fine in 7.06.
- Compile View01 and run.
- First you will see the single table example.
- Press the Multi-table example menu item.
- You will the "Active Audits" list. This list has less than number of records to show the navigation buttons. However this browse has a title that is not being displayed.
- Click on the "Other Audits" button. You see that the list has changed, but the browse title is not displayed and the navigation buttons do not appear. Refresh the web page and the title and navigation buttons will appear.
- Click on the "Closed Audit" button. You can see that the browse title does not change.
Bruce,
Even though 7.13 fixed some bugs, new bugs have been introduced. My applications are worse off in 7.13 than 7.12. We need a break. Can we get new releases that just fixes bugs and does not introduce any new refractoring for while? As you know, I need new features as bad as anyone else.
Thanks
Rob
[attachment deleted by admin]
-
Hi Ashley & Rob,
Thanks for the report, and the example
>> I no longer have the navigation buttons for that browse in version 7.13.
fixed.
>> This browse has a title that is not being displayed.
fixed.
>> Click on the "Closed Audit" button. You can see that the browse title does not change.
fixed.
>> Even though 7.13 fixed some bugs, new bugs have been introduced.
yes, although the scope of the bugs introduced is quite narrow, whereas the items being fixed through the 7.11 through 7.13 builds are much wider in scope - in order to do some things sometimes big changes are required. Alas sometimes the big changes can lead to some refinements being necessary.
>> We need a break. Can we get new releases that just fixes bugs and does not introduce any new refactoring for while?
depends on your definition of a "while", but yes I'm trying to keep the builds coming fast, and the fixes as low-impact as possible for this week. that said I've got an enormous amount of things to get done before Devcon, so there will likely be some "big" tweaks coming in the relatively new future.
I know it's painful, but the end result is worth it. There are two basic strategies though which I recommend; Either
a) try builds as quickly as possible after the release. It's a lot easier to make small tweaks and update a fresh build than it is to do a build at an arbitrary time.
Or
b) hold back and get a release say a week after it's up. That way you ship all the "obviously broken" stuff. That said, this approach can work less well if you have a lot of custom code - the more "custom" the app the more likely it's not in my testing patterns.
cheers
Bruce
-
Thank you Bruce!
Ashley
-
I know it's painful, but the end result is worth it.
I agree. I've been down this road with NT4, NT5, NT6, and now NT7. It always gets worked out.
Don