[V17.0.284] Bug with moving events with enabled "Event length"

musko wrote on 8/7/2019, 12:31 PM

In different cases I have problem with moving events on timeline.
As you may see when I drag event on header (on screenshot is displaced, but you can trust me I drag on header) one event move but another two events not moved.

Can someone confirm this bug?

Comments

VEGASPascal wrote on 8/7/2019, 12:38 PM

I believe we need more information. What happens with your grouping? If you drag the header the clip is not selected (yellow borders).

Marco. wrote on 8/7/2019, 12:52 PM

Never seen this. As MagixPascal mentioned it's strange your events are not selected when you grab them on the header. It seems your mouse-pointer is misaligned. A Windows issue? Do you use any scaling in Windows?

musko wrote on 8/7/2019, 1:04 PM

No my mouse-pointer is not missaligned. Video is not exactly, I don't know why windows screen recorder do this. You can trust me I click on header. (I can record this behavior on mobile phone)

Yes, when I click on header clip not slected (yellow borders).
But when I click on thumbnail of event clip is slected (yellow borders).
but still event can't move when I click on header. Only can move when I clikc on thumbnail or anywhere on event

musko wrote on 8/7/2019, 1:14 PM

Interesting behavior with moving events (drag on header) when I zoom in or zoom out timeline:

This is explain what is problem
@VEGASPascal
@Marco.

matthias-krutz wrote on 8/7/2019, 1:58 PM

Events can not be moved when the event length text is clicked. Even if this text has just been switched off, this area is inactive. This inactive area can cover the take information.

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

musko wrote on 8/7/2019, 2:20 PM

But such a "problem" has never been in version 16

matthias-krutz wrote on 8/7/2019, 2:38 PM

Yes, in VP16 the event length could not be displayed in the header. I think if you let them turn off until there's a bug fix, it works too.

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

Marco. wrote on 8/7/2019, 3:03 PM

Good finding. I couldn't repro this issue because I have the Event Length Display disabled.

musko wrote on 8/7/2019, 3:28 PM

@matthias-krutz you are right! When I disable new function show "Event length" then moving event working correctly.
I rename this post.

@VEGASPascal I hope that in next version this small bug resolve.

VEGASDerek wrote on 8/7/2019, 3:52 PM

We will look into this issue. Right now the mouse click is being handled within the Event Length field so the user can double click on it and manually edit it. Obviously this is causing issues, so we will see if we can work around this.

musko wrote on 9/23/2019, 10:31 AM

In version 17.0.321 is this problem not solved.
This is sad.

fr0sty wrote on 9/23/2019, 10:50 AM

They had over 40 bugs they addressed in this update, they probably ran out of time to get more in and didn't want to delay people suffering from the more serious bugs from getting work done.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

musko wrote on 9/23/2019, 10:52 AM

I know and I accept, but this is still sad

matthias-krutz wrote on 9/23/2019, 3:48 PM

The problem is at least partially solved. There is no phantom "event length" anymore. To make better use of the limited space, I often turn off the event headers.

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

vkmast wrote on 9/23/2019, 4:12 PM

Would this work for you?

Former user wrote on 9/23/2019, 4:14 PM

Its not the same, just reminds me of the track header name area. If you select that area you can drag and reposition the tracks up or down, obviously not if its in edit mode.

 

matthias-krutz wrote on 9/23/2019, 4:36 PM

The implementation as with the track headers will be more difficult at the events. But it would be the right one.

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

NickHope wrote on 9/24/2019, 12:35 AM

The problem is at least partially solved. There is no phantom "event length" anymore. To make better use of the limited space, I often turn off the event headers.

For me, in VP17 build 321, a phantom "event length" area still exists on events that are too short to display event length. Events cannot be moved by dragging this area.

musko wrote on 9/24/2019, 1:01 AM

@NickHope same here.

Sometime I use minimized track height (when I have a lot of tracks) and in this case is unusable moving events.

musko wrote on 9/24/2019, 10:36 AM

Would this work for you?

No this not work for me.

As I wrote, I use minimised track height (on projects with more tracks) and in this case I can't move event when I have "Show Event Length" ON.

😢😢😢

 

musko wrote on 9/24/2019, 10:39 AM

The problem is at least partially solved. There is no phantom "event length" anymore. To make better use of the limited space, I often turn off the event headers.

@matthias-krutz no, phantom "event length" is not solved in 17.0.321

 


matthias-krutz wrote on 9/24/2019, 11:28 AM

I have to correct myself, nothing has changed in the behavior yet.

musko wrote on 9/24/2019, 11:38 AM

😢😢😢

VEGASDerek wrote on 9/24/2019, 3:16 PM

I'll be honest with you, this bug was overshadowed by other issues and fell off our radar screen.

I have spent some time the last couple days and created a solution for this which should fix this annoyance. My apologies.