question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. ItĀ collects links to all the places you might be looking at while hunting down a tough bug.

And, if youā€™re still stuck at the end, weā€™re happy to hop on a call to see how we can help out.

Solid stroke mismatch in UI

See original GitHub issue

šŸ› Bug

The solid line shown in the graph, is displayed incorrectly as a dashed line in the table.

To reproduce

When I groupby the curves by stroke, the solid curve shown in the graph (see the screenshot below)

Screen Shot 2022-10-26 at 5 06 14 PM

is depicted as a dashed curve (the top column) in the table (see the screenshot below). Note that the top columnā€™s stroke is style="stroke-dasharray: 12, 3, 6, 3, 3, 3, 3, 3;" (which correspond to solid curve in the graph), and the bottom columnā€™s stroke is style="stroke-dasharray: 12, 3, 6, 3;" (which correspond to dashed curve in the graph).

Screen Shot 2022-10-26 at 5 06 30 PM

Expected behavior

The solid curve is shown as solid in the table.

Environment

  • Aim Version 3.14.1
  • Python version 3.10
  • pip version 22.2.2
  • macOS chrome

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
twni2016commented, Oct 28, 2022

Thanks for a quick fix!

1reaction
KaroMouradcommented, Oct 27, 2022

Since we are processing stroke styles before rendering stroke badges in the table, these stroke-dasharray 12, 3, 6, 3, 3, 3, 3, 3; value is valid.

Have found an issue with the processing part. Already fixed the bug related to ā€˜stroke-dasharray: noneā€™ values. @twni2016 If you could, please check out the branch fix/fix-solid-stroke-rendering-issue-in-table and let me know if the issue has been fixed for you.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Neuroimaging Paradigms to Identify Patients for Reperfusion ...
study was an observational study of IV tPA-treated patients for which target perfusionā€“diffusion mismatch was defined as mismatch volume (PWIā€“Ā ...
Read more >
What Is the ā€œOptimalā€ Target Mismatch Criteria for Acute ...
We aimed to compare Perfusion Imaging Mismatch (PIM) and Clinical Core Mismatch (CCM) criteria in ischemic stroke patients to identify theĀ ...
Read more >
Comparison of Two Software Packages for Perfusion Imaging
Abstract: Purpose: Automated postprocessing packages have been developed for managing acute ischemic stroke (AIS).
Read more >
ā€œClinical-CT Mismatchā€ and the Response to Systemic ...
Background and Purposeā€” Mismatch between clinical deficits and imaging lesions in acute stroke has been proposed as a method of identifying patients who...
Read more >
font-weight - CSS: Cascading Style Sheets - MDN Web Docs
The font-weight CSS property sets the weight (or boldness) of the font. The weights available depend on the font-family that is currentlyĀ ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found