Hello all,
I am at a loss and need your crowd inteligence.
For my music repertoire I created a workbook with a songlist, that I have automated with some useful macros. Basically I can filter the songlist, open youtube videos to the song on youtube and also have put the chord sheets in the workbook, that I also can access from the central "songlist" worksheet. For convinience of stepping through the titles and show the chord charts at the same time I made use of the create new window (pane) and grouped those 2 windows vertically. That was a little bit fuzzy and trial and error until I had it function the way I wanted. The code is not so pretty - but it worked as intended.
The full file is at the moment around 600K bit and contains approximately 50 sheets with only text data. I would think that is nothing excel would get sweaty about.
As to step through the titles from the songslist I entered the code in the Worksheet_SelectionChange event so I can easily step down with the arrow keys to get the next chordsheet. This should placed right next to the songlist. Assuming there is already a second window of the same workbook open, I have this close function in the code - if nothing was open yet, the on error resume next catches that case.
For some reason the code runs in the normal usage of the automated songlist sheet incredibly slow (nearly 10 seconds on a modern laptop with I7 intel core).
When I debug the code it runs quick - now brakes, not waiting - every command seems to be executed instantly. The big question is, why the worksheet does not match the performance in exceution during Worksheet_SelectionChange event. The code I have under suspicion is yellow marked. During the worksheet event I realize, that the closing of the second pane with the chordsheets takes long. In debugging it works like a breeze (quick).
Please find the code snippet of the Worksheet_SelectionChange event procedure and the MSO version I am using.
Hope one of you can come up with an idea - I am at a loss now!
Cheers
Stefan
I am at a loss and need your crowd inteligence.
For my music repertoire I created a workbook with a songlist, that I have automated with some useful macros. Basically I can filter the songlist, open youtube videos to the song on youtube and also have put the chord sheets in the workbook, that I also can access from the central "songlist" worksheet. For convinience of stepping through the titles and show the chord charts at the same time I made use of the create new window (pane) and grouped those 2 windows vertically. That was a little bit fuzzy and trial and error until I had it function the way I wanted. The code is not so pretty - but it worked as intended.
The full file is at the moment around 600K bit and contains approximately 50 sheets with only text data. I would think that is nothing excel would get sweaty about.
As to step through the titles from the songslist I entered the code in the Worksheet_SelectionChange event so I can easily step down with the arrow keys to get the next chordsheet. This should placed right next to the songlist. Assuming there is already a second window of the same workbook open, I have this close function in the code - if nothing was open yet, the on error resume next catches that case.
For some reason the code runs in the normal usage of the automated songlist sheet incredibly slow (nearly 10 seconds on a modern laptop with I7 intel core).
When I debug the code it runs quick - now brakes, not waiting - every command seems to be executed instantly. The big question is, why the worksheet does not match the performance in exceution during Worksheet_SelectionChange event. The code I have under suspicion is yellow marked. During the worksheet event I realize, that the closing of the second pane with the chordsheets takes long. In debugging it works like a breeze (quick).
Please find the code snippet of the Worksheet_SelectionChange event procedure and the MSO version I am using.
Hope one of you can come up with an idea - I am at a loss now!
Cheers
Stefan
