Community Blog

Hey everyone!

This is my third weekly report for my GSoC project. This will include all the work from the past week. It includes my key accomplishments up to this point, the tasks that have given me trouble, and my plan for the next week.

Key accomplishments

-Finished Labels

The labels for the rows have now been added--and they are re-sizable!

-Meta Rows

The three meta rows are now included in the timeline. Those are time signature, key signature, and

I decided to make a flow chart to show the various processes of breakpads and where they took place:

[inline:muse_breakpads.png]

Next I made a Qt example based on the Qt breakpad integration example from here:
https://github.com/JPNaude/dev_notes/wiki/Using-Google-Breakpad-with-Qt

My source code of the example is locate here:
https://github.com/gsocnikos/musescore_crash/tree/master/qt_example/qt_…

My build is located here:
https://github.com/gsocnikos/musescore_crash/tree/master/qt_example/bui…

I compiled it using CMake and MSVC2015

When you run the exe it will show up a Qt window for a few seconds and after that the crash

github: https://github.com/aryamanvinchhi/MuseScore

This week I worked on implementing a way to detect a user’s keyboard layout. After the keyboard layout is known, the appropriate shortcut list can be selected. The startup wizard is now slowly taking shape.

Key Accomplishments Last Week:
1. Configured the startup wizard to ask the user for his keyboard layout based on his system language.
2. Implemented a way for a user to choose from a universal list if his keyboard layout is not present on

Hello!
This week, I have completed the navigation commands, and have started working on palette navigation.
I'd like to thank everyone who provided feedback on which approach to use to make the palettes keyboard accessible. Adding keyboard shortcuts for every palette symbol did not seem feasible, so the other approach which uses the palette search and palette navigation will be implemented.

Key accomplishments

Completed next-element and prev-element commands:

I removed some remaining bugs from the navigation commands next-element and prev-element.

I was able to compile breakpads client in windows environment with qmake(Qt creator) and mingw32 with this source code:
https://github.com/gsocnikos/musescore_crash/tree/master/windows_client

This is a simple example that generates a crash and creates a minidump file under c:\temp

The next step is to produce the symbol file from the executable. For this step breakpads comes with a precompiled tool called dump_syms. I tried all possibles ways using dump_syms to generate the sym file and I couldn't make it. dump_syms can not recognize

Hey everyone!

This is my second weekly report for my GSoC project. This will include all the work from the past week. It includes my key accomplishments up to this point, the tasks that have given me trouble, and my plan for the next week.

Key accomplishments

-Resizing bug fixed

After removing a bunch of code, resizing the screen now does not mess up the scrollbar. Also, undocking and docking works well.

-Selection Box

There now exists a blue box

I am having issues on compiling breakpads on windows

I actually succeeded to compile libbreakpad.a using msys and mingw32

But I overpass some issues using this code for strtok_r which I found from stack overflow:

char* strtok_r(
char *str,
const char *delim,
char **nextp)
{
char *ret;

if (str == NULL)
{
    str = *nextp;
}

str += strspn(str, delim);

if (*str == '\0')
{
    return NULL;
}

ret = str;

str += strcspn(str, delim);

if (*str)
{
    *str++ =

Hello!

I have been working on navigation commands to get to the next element and previous element of the score.
Below, I have written the key tasks I have completed, some tasks that stalled and the plan for next week.

Key accomplishments so far

I have been working on two navigation commands, next element and previous element. These commands select the next or previous element of the score. Elements like fingering and other note attached elements, articulation, lyrics, annotations and

github: https://github.com/aryamanvinchhi/MuseScore

For implementing my project idea, the first step that I want to complete is identifying the user’s keyboard layout. To do this, I will use the user’s locale to establish the user’s language and then present the user with a list of the most commonly used layouts in that language. The user can then choose his layout from this list. For instance, if the user’s locale is en-US then the list would contain the following options: QWERTY, AZERTY,

Hey everyone!

This is my first weekly report for my GSoC project. This will include all the work I did preceding the "official" coding time. It includes my key accomplishments up to this point, the tasks that have given me trouble, and my plan for the next week.

Key accomplishments

-Created the base of the timeline

This includes creating the tool that appears at the bottom of the screen, linking the tool to the view menu, and allowing it to