I'm still struggling with the white lines that app...
# compose-desktop
d
I'm still struggling with the white lines that appear on the right side of grids (including actual Grids and columns with rows). Its been determined that this is a floating point issue that is poorly handled by the frameworks fractional pixel rendering (thank you @Michael Paus and @romainguy). I would greatly appreciate anyone that has an idea of how to get rid of them to share. They are a major eyesore when we are demoing our app. I have tried rendering these with Grids (e.g. LazyVerticalGrid) as well as Rows and Columns. I can't fix the size of the small squares because its a responsive design, that requires the wells (squares) to resize for the plate size. Attempting to add a bottom row of pixels doesn't work.
m
I cannot give any other advice than to report this issue because I think it is an implementation bug in the grid rendering. A further option would be to implement this yourself via some canvas rendering but of course I don’t know what you actually want to achieve and whether this would be a viable solution.
d
@Michael Paus I plan on reporting it tomorrow. I've thought about creating a Composable that renders the wells (squares), but it will be a PITA. The wells are also buttons that pull up data when you click them. Thank you again for your advice.
m
That shouldn’t be too difficult to implement. You just have to compute the cell coordinate from the location of the mouse click.
☝️ 1
r
Setting the issue aside, this really calls for a custom component indeed.
m
The UI isn't complex, try rendering it in Canvas.
y
This looks very neat. is this opensourced @dleuck? if not, could you highlight what custom libraries you used for building the app
d
@Michael Paus There is more going on than displaying squares, but porting it to a Canvas isn't that big a deal. Claude can do most of the work. That being said, it would be better if their LazyVerticalGrid composable worked. That rendering bug makes it pretty useless.
This looks very neat. is this opensourced @dleuck? if not, could you highlight what custom libraries you used for building the app
Thank you @Yogeshvu. I'm not using any external libraries, although I will probably add RSyntaxTextArea from Fifesoft for the TinyEdit composable I wrote for editing the data files we use as input. I wrote the parser we use to read in the Perkin Elmer data format for plates. Claude was very helpful. re: Open Source - ClearWell is a commercial project for companies doing drug discovery, but we have considered making the core open source so it would be easier for others to build analytics plugins for assay analytics.
🙌 2
m
It will be interesting to see if Claude will introduce the same rendering error into the code or not 🧐. If not, then that would finally convince me of the usefulness of AI 😉.
d
@Michael Paus Claude did not 🙂 In fact, she nailed it on the first try. No rendering issues, and Claude introduced better responsive behavior when the window resizes even though I didn't ask for it. The well behaviors took a little longer. I recommend giving Claude a try.
m
I probably should then 😉. (But why “she”? Claude is a male name, isn’t it? Otherwise it would be Claudine.)
d
It's a French unisex name. Today Claudia and Claudette are more common, but I've met more than one woman named Claude. Sometimes its a shortening of the longer variants.
💡 1