User Profile & Activity

Yudi Member
Page
of 259
Posted: September 2, 2016 6:49 AM

The layout problems in iOS 8 has been forwarded to Crosslight development team. It is reported under CROS-1172.

Since new app submission should be done on iOS 9. We'd like to inform you that we don't currently have urgency to address issues for versions below iOS 9. However, any feedback concerning this issue are welcomed.

Posted: September 2, 2016 4:48 AM

This problem has been forwarded to Crosslight development team and submitted under CROS-1171. I will keep this thread updated with any news I heard from the team regarding this.

As usual you will create a new CROS ticket for the dev team after reproducing the bug. This is the way it should be. The worse thing about it is that it will take weeks or months to get the fix.

Sorry for any inconvenience this problem may have caused you. I will informed this to the team to consider your concern. Again, thank you for the valuable feedback.

Posted: September 1, 2016 6:55 AM

Sorry for the delay in sending this.

I got the same result after follow the steps mentioned in your initial post. I tested on both, Android and iOS, with the same result.

I'll have this discussed with Crosslight development team and will get back to you today.

Updated on September 5, 2016 4:30 AM
Reason: update response

Is this the intended behaviour? Is it possible to cancel the changes when navigating back? A sample or short explanation would be nice.

Yes, it is intended behavior. It's AutoSaveChangesOnDismiss property which allows to configure whether to save the changes upon UIFormViewController/FormFragment dismiss.

In the past releases, this feature is always enabled. Starting on Crosslight 5 Update 1, the default value for this new property is true to maintain compatibility.

It is possible to cancel the changes when navigating back. Simply override AutoSaveChangesOnDismiss property in UIFormViewController (for iOS) or FormFragment (for Android); then return its value to false.

Hope this helps.

Posted: September 1, 2016 4:45 AM

Apologize for the delay in sending this.

I started my investigation by modifying basic-inventory sample of Crosslight.

The changes are:

  • Add HasReminder property in Item class (see Item.cs)
  • Add VisibilityBinding attribute to SoldDate and set its Path to HasReminder (see Item.FormMetadata.cs)
  • Set the value of HasReminder in ViewModel (see Navigated in ItemEditorViewModel.cs)

I set HasReminder to true when user edit an item (parameter.Data != null. not new item). The SoldDate appear as expected. Try to add the VisibilityBinding attribute to another editor control (which EditorType is TextView) also works without problem.

I uploaded my sample, VisibilityBinding_Sample.zip, in OneDrive. Please have a look at the sample and feel free to let me know if you find anything that I might miss during my attempt in order to reproduce the problem.

Posted: September 1, 2016 3:33 AM

Apologize for the delay in sending this.

This problem has been forwarded to Crosslight development team. The report is filed under CROS-1170.

I will keep you informed when the nightly build is ready to be evaluated.

Sorry for any inconvenience this problem may have caused you.

The problem has been resolved. Thank you very much for the feedback.

Posted: August 26, 2016 7:12 AM

Sorry for the delay in sending this.

The problem has been forwarded to development team of Crosslight for further investigation. The report is filed under CROS-1169.

I'll keep you informed with any news I heard from the team regarding CROS-1169.

Posted: August 18, 2016 2:13 AM

Hi Tor,

Please allow me to check the progress with the ClientUI development team. I will get back to you with any news I heard from the team.

Posted: August 12, 2016 3:47 AM

Thank you for the information. I can replicate the issue after removing RefreshGroupItems().

I have submitted the reported problem to Crosslight development team. It is filed under CROS-1168.

I will keep you updated with any news I heard from the team regarding CROS-1168.

Posted: August 11, 2016 2:46 AM

I tried to enable AllowAutoDataCaching on following WebGrid sample files: ClientBinding_Paging.aspx and ClassicPagingUsingCustomDataRetrieval.aspx. Save all the changes and view the grid in browser. No problems found when navigating to page 2.

I'm willing to advise you further but in order to do so I would need you to elaborate on your specific scenario and possibly provide me with a simple sample which replicates the issue and step-by-step guide that I can use to observe the problematic behavior.

All times are GMT -5. The time now is 3:17 AM.
Previous Next