Skip to main content
A
AtonMusic
Known Participant
January 28, 2019
Answered

PF_EventExtra->effect_win.current_frame BUG

  • January 28, 2019
  • 1 reply
  • 1048 views

Hi There,

either I am doing something very wrong or this is indeed a serious bug.

According to SDK Guides this should report the width of the window in which the Plug-In Resides. The Effect List window where one adjusts the effect.

I take you guys added this feature so that a plug-in can react to the user broadening the window and adjust their interface.

Anyway, here is the bug.

I create an ARB Param and set its width to a default of 200 - wanting to later adjust it to the size of the effect list width.

Here is what happens when I call PF_EventExtra->effect_win.current_frame. It will ALWAYS report the width of the arb minus 4 pixels. No matter how wide the user broadens the effect list view.

This way it becomes impossible to respond to user changes. Why it reports the width of my ARB I dont understand. I KNOW how wide my arb is, as I set its width -)

Clumsy Workaround for anyone who is experiencing this

Set the ARBs width when you create to the max size of its type. Or 100000. Or whichever value you believe will exceed the amount of pixels any future display will be able to physically hold... Just make sure that the value you do pick WILL be large than ANY display's width...

Setting this ridiculous width will somehow make PF_EventExtra->effect_win.current_frame return the actual width of the effect list window.

This topic has been closed for replies.
Correct answer Bruce Bullis

Interesting; since we introduced Arb parameters (in AE 4.0, 1998), you're the first developer to complain about that behavior.

I don't think the host respecting your plug-in's stated max value, is a bug.

Why it reports the width of my ARB I dont understand. I KNOW how wide my arb is, as I set its width -)

You knew the maximum stated value, but your effect cannot know the current PF_EventExtra->effect_win.current_frame.

As you mentioned, setting a large maximum width obviates any difficulty.

1 reply

Bruce Bullis
Bruce BullisCorrect answer
Legend
January 29, 2019

Interesting; since we introduced Arb parameters (in AE 4.0, 1998), you're the first developer to complain about that behavior.

I don't think the host respecting your plug-in's stated max value, is a bug.

Why it reports the width of my ARB I dont understand. I KNOW how wide my arb is, as I set its width -)

You knew the maximum stated value, but your effect cannot know the current PF_EventExtra->effect_win.current_frame.

As you mentioned, setting a large maximum width obviates any difficulty.

A
AtonMusicAuthor
Known Participant
January 29, 2019

bbb_999  wrote

Interesting; since we introduced Arb parameters (in AE 4.0, 1998), you're the first developer to complain about that behavior.

I get it

To me though, when asking for the Window's current frame size I would expect that it would report its current size without me having to first put something insanely large in to it... The EffectListWindow has a size before our plug-in becomes instantiated so I'd gather that it would be aware of its intrinsic size.

In regards to other developer having not complained... The plugs I have seen from 3rd pty. running in premiere either use standard SDK sliders or controls which aren't resizing with the EffectListWindow in which case that particular value would never be of any concern. In our case this posed an immediate concern.

Anyway, having figured out the workaround - this does not post a concern any longer !!

Thx

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices