I'm afraid to say it's still happening. I even tried to downgrade the drivers, but nothing.

Hello, I think another option could be to change the border thickness and roundness of the active area. This would make it stick out, while gaining a few extra pixels to work with, and also it would tackle a bit the annoyance of resizing panels:

Can you explain this in more detail? Do you mean to add more lines?

I closed it since this issue does not occur anymore. There are other issues with edge cases though, but only affecting UI so I'll open another report.

Hi, as a frequent user of the VSE, I don't find them distracting, but rather the opposite as you don't have to make guess work to know if the strips are aligned with the time. What I'd do instead (kind of feature/improvement request) is to draw lines only for the text being displayed (for example 5+00, 5+01, etc.). This way it won't become as crammed as it does now.
Of course, making the lines opcional is an even better solution as it lets you choose.

I have updated the drivers but it keeps happening. I have also tried in another PC (noticeably more powerful) and it works as spected.

Hi, I don't know if it's possible but wouldn't a simple animation (like showing the 3 dots cycling like . , .. , ...) be preferable to make sure Blender it's not freezing?
Many times I'm not sure if something happened to Blender, and other times Blender just goes blank for a while (not responding), so any feedback to the user would be neat.
The ideal solution would be a loading bar, but I know that's harder to implement, or even some info of what's loading (Shaders, models, hair, etc.)

Hm, it does solve the issue. I should have done that before reporting. Sorry for the trouble.

Absolutely. Like I said, if a solution can be found to freely manipulate the pivot point without losing the selection, that would certainly solve this. Until then however, removing the current workflow would be a regrettable downgrade.

I solved this issue (and many more) directly in the addon's git

Hi, tried with 2.83.9, 2.90.1, 2.91.0 and a recent release of 2.92. I could only replicate the bug with 2.83.9 and 2.90.1, so the problem is fixed with 2.91.0 and newer.

Okay now... This is strange. I just downloaded 2.68 and I did the tests. It turns out that with 2.68 version, it allows you to save, but not to open files, while in 2.7 and newer can't save nor open

I can confirn that it is a bug. As I mentioned in the description of the problem, in blender 2.69 and in older versions worked with the same set up that in recent versions stops working

In T73588#865739, @Richard Antalik (ISS) wrote:

Can confirm program not responding, not crash.

stuck at printf("Read blend: %s\n", filepath);

	blender.exe!BKE_blendfile_read(bContext * C, const unsigned char * filepath, const BlendFileReadParams * params, ReportList * reports) Line 417	C
 	blender.exe!WM_file_read(bContext * C, const unsigned char * filepath, ReportList * reports) Line 636	C
 	blender.exe!wm_open_mainfile__open(bContext * C, wmOperator * op) Line 2239	C
 	blender.exe!wm_handler_fileselect_do(bContext * C, ListBase * handlers, wmEventHandler_Op * handler, int val) Line 2265	C
 	blender.exe!wm_handlers_do_intern(bContext * C, wmEvent * event, ListBase * handlers) Line 2749	C
 	blender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 2802	C
 	blender.exe!wm_event_do_handlers(bContext * C) Line 3181	C
 	blender.exe!WM_main(bContext * C) Line 421	C
 	blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 520	C
 	[Externí kód]

As soon as you cancel selection in console, execution continues

I may add, that when I quit Blender during debugging session (MSVC), console will wait for key press. I am not able to start new session until I make key press.