You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I am sorry about your inconvenience.
Could you let me know what TestPlan you are working? also let me know what
browser you are using.
For now, I have just tested some of TestPlans but the speed is acceptable
for me. Not sure that the issue is due to sever environment.
Have you use template? You can store TestDataCategorizations patten for
Message/Segment and then apply it to other TestStep.
after one or two expands of a segment the client browser slows down or
even crashes making it difficult to edite. This is a horrible user
experience for an editor. I propose either fixing the browser logjam or
providing an alternate way to input the test categorization data in bulk
such as csv import.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/ usnistgov/tcamt/issues/18>, or mute the thread<https://github.com/
notifications/unsubscribe-auth/AMw9_dEoBYKONKUNXGNdLgtZ9cgdiJ3Kks5
r0PpfgaJpZM4NKum1>.
There are some improvements to speed issues. I will deploy the tool at tomorrow morning (5/1 Monday).
In particular, Exapnd-all may crash the browser due to user's additional action while working. To prevent this, we added code to prevent user input.
There will be further improvements in speed over the next one to two weeks. If this is not enough, you will implement external input using CSV files as you are invited.
From Eric,
Chrome and there is a noticeable performance issues after expanding
segments more than a couple fo times see screen shot below.
Thanks,
Eric
Eric M Haas, DVM, MS
Health eData Inc
211 South Jefferson Street, Napa, CA, 94559
707.227.2608|Skype: haas.eric1
[email protected] [email protected]
On Thu, Apr 27, 2017 at 2:37 PM, Jungyubw [email protected] wrote:
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
The text was updated successfully, but these errors were encountered: