Crash - 5.2 SR-4 (5.2.0.0110) - Logs Attached
As best I can guess, either a touchpad gesture or a fat finger on an arrow key caused L5 to change to a parallel resource (to the commentary I was highlighting), In the subsequent string of right & left arrow key commands to try to navigate back to my resource, L5 crashed. Log files with today's date are as follows:
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB
Comments
-
Definitely one for the Logos Developers!
"InvalidOperationException: Layout measurement override of element 'LDLS4.OwnerDrawn.OwnerDrawnControl' should not return PositiveInfinity as its DesiredSize, even if Infinity is passed in as available size."
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Definitely one for the Logos Developers!
"InvalidOperationException: Layout measurement override of element 'LDLS4.OwnerDrawn.OwnerDrawnControl' should not return PositiveInfinity as its DesiredSize, even if Infinity is passed in as available size."
Thanks, Dave. L5 is just fine... started right up & continued using it all day in the same layout.
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
Dave
===Windows 11 & Android 13
0 -
BillS said:
As best I can guess, either a touchpad gesture or a fat finger on an arrow key caused L5 to change to a parallel resource (to the commentary I was highlighting), In the subsequent string of right & left arrow key commands to try to navigate back to my resource, L5 crashed
I will create a case for Development to investigate.
0 -
Angela Murashov said:BillS said:
As best I can guess, either a touchpad gesture or a fat finger on an arrow key caused L5 to change to a parallel resource (to the commentary I was highlighting), In the subsequent string of right & left arrow key commands to try to navigate back to my resource, L5 crashed
I will create a case for Development to investigate.
This should be fixed in 5.2a Beta 5. You will see this fix once 5.2a ships to the stable channel.[:)]
0