What did you do this week?

This week, I tackled the ComboBox2D icon flaw, which was addressed using Pull Request (PR) #576. The problem arose when we added a ComboBox2D to the TabUI. The TabUI would propagate the set_visibility = true for all its child elements, causing the combobox to appear on the screen without the icon change. To fix this issue, #768 updated the set_visibility method of the UI class, ensuring that the icon change was applied correctly.

Next, I focused on the textbox justification. As discussed in our meeting, I added a new property called boundingbox to the TextBlock2D. However, I encountered a problem when resizing the TextBlock2D. The `vtkTextActor` property would switch from `SetTextScaleModeToNone` to `SetTextScaleModeToProp` , which would scale the font according to the position1 (lower left corner) and position2 (upper right corner) of the UI. This inconsistency in font scaling resulted in misaligned text actors. I spent some time investigating this issue, and you can find my progress in the ongoing PR #803.

Additionally, I started working on creating a Scrollbar component by inheriting the LineSlider2D. I made adjustments to the position and other attributes to make it function as a scrollbar. However, I encountered some confusion regarding how to separate the scrollbar component from other elements and determine what should be included in the scrollbar itself.

Did you get stuck anywhere?

I faced a challenge while working on the text justification. It took me several days to identify the root cause of the occasional malfunctioning of the TextBlock2D. Atlast, I found out the reason behind the issue.

What is coming up next?

Next week, I have several tasks lined up. Firstly, I will be working on the CardUI PR #398. Additionally, I plan to complete the segregation of the scrollbar component, ensuring its independence and clarity. Lastly, I will be working on issue #540, which involves updating the use of the `numpy_to_vtk_image_data` utility function.

What did you do this week?

This week, I continued tweaking the text justification PR #790 and encountered a new issue when combining both justification and vertical_justification. The problem arose because the vertical_justification did not take into account the applied justification, resulting in unexpected behavior. I focused on resolving this issue by ensuring that both justifications work together correctly. Additionally, during the weekly meeting, we discussed the problem and decided to introduce new properties such as boundaries and padding to enhance the functionality of the text justification feature.

Furthermore, I started working on PR #576, which aimed to address the flaw in the icon of the combobox. While investigating this issue, I discovered related problems and PRs, including #562, #731, and #768. The main challenge was related to the propagation of the set_visibility feature of the UI, causing the combobox to automatically open its options. To overcome this issue, I requested the author of PR #768 to rebase their pull request as it can be a solution for the issue.

Did you get stuck anywhere?

A significant portion of my time was dedicated to resolving the text justification issue when both justification types were combined. It required careful analysis and adjustments to ensure the desired behavior.

What is coming up next?

For the upcoming week, I have the following plans:

1. Work on modifying the text justification implementation to address any remaining issues and ensure compatibility with other features.
2. Begin the implementation of the scrollbar class from scratch to provide a robust and customizable scrollbar element.
3. Focus on completing the resolution of the icon flaw issue by collaborating with the relevant stakeholders and ensuring the necessary modifications are made.

What did you do this week?

This week, my focus was on reviewing pull requests (PRs) and issues related to the user interface (UI) of the project. I meticulously went through each PR and issue, identifying those specifically associated with UI improvements. To streamline the process, I categorized them accordingly under the UI category. One of the key tasks was PR #499, which involved the implementation of SpinBoxUI. After rebasing the PR, I identified an alignment issue with the textbox component.

To resolve this issue, I started by investigating the root cause. I discovered that the alignment was initially based on the position of the parent UI, which caused the text to extend beyond the boundaries of the textbox. To rectify this, I devised a solution where I calculated the background size of the textbox and adjusted the text's position accordingly. By aligning the text with the calculated size, I ensured a proper and visually appealing alignment within the textbox.

To provide a clear understanding of the improvement, I have prepared a comparison of the textbox alignment before and after the modifications:

Before:

After:

Did you get stuck anywhere?

Fortunately, I didn't encounter any significant challenges this week.

What is coming up next?

Looking ahead, here's what I have planned for the upcoming week:

1. Completing PR #790 - Fixing Textbox Alignment

2. Wrapping up PR #499 - SpinBoxUI

3. Initiating PR #576 - Icon Flaw in ComboBox

Hello All!

I'm thrilled to announce that I'll be participating in Google Summer of Code (GSoC) for yet another year. To catch a glimpse of my previous journey, check out my experiences here.

During the community bonding period, we had our first GSoC meet, where we got acquainted with the program's rules and regulations. It was an excellent opportunity to virtually meet my fellow contributors and discuss our upcoming projects. Excitement filled the air as we exchanged ideas and set goals for the summer ahead.

Stay tuned for updates on my GSoC project as I share my progress, challenges, and breakthroughs along the way. I'm grateful for the opportunity to be part of this remarkable community and can't wait to witness the incredible projects that will unfold during GSoC 2023.