Jump to content
Alloder.pro: about Allods with love
Search In
  • More options...
Find results that contain...
Find results in...

New program for writers

We turn from quantity to quality and tell you how we will supplement the Allods Team program with rewards in rubles.


The new Updater

Let us to introduce the new addon updater software and to share the details

Read more

Alloder 2.0

We have started the process of project evolve, and this relates not only, and not even primarily of the site's view

Read more

Toggle transparent input from LUA.


Recommended Posts

As far as I've seen, nope.

The only function that comes close to this is :Enable(false) but it grays textures.

An idea that I just had is; you could create two main forms with the same sizes, one with TransparentInput true, one false with PickChildrenOnly true and then :AddChild(widget) back and forth as DND is necessary.

Link to comment
Share on other sites

Transparent input значит мышкой можно тыкать насквозь, т.е. панель "прозрачна" для тыканья мышкой.

Если оно false то мышка тыкает не сквозь панель (например в 3D view или в другие виджеты под нашим) а в панель - например для перетаскивания или для нажатия кнопки.

Надеюсь максимально подробно объяснил. Например мы создаем большое прозрачное/полупрозрачное окно, например карту в реальных масштабах нокоторая должна быть видна всегда, как в диабло 2 например - т.е. она всегда полупрозрачная и в центре экрана, т.е. на ней можно сфокусироваться (глазами, не ЛУА )) ).

В ней естественно должен быть Transparent Input - чтобы сквозь карту можно было тыкать мышкой в инвентарь, по врагам, в окно трейда и т.п.

Либо например нам нужна панель в которой (или которую, или которую за что-то) нужно перетаскивать. Если Transparent input == true то мы не можем ее перетаскивать - нажатия передаются в то что под ней. Или кнопки - кнопки тоже не будут нажиматься если в них стоит "transparent unput" (хотя на кой хер это надо? :) Но прям щас у меня уже появились идеи).

Link to comment
Share on other sites

  • 1 month later...

Pick children only allows the transparent input to only be applied on the <Children> of the panel specified.

<TransparentInput>false</TransparentInput><PickChildrenOnly>true</PickChildrenOnly> Makes the input for the panel click through-able but not its children.

<pickObjectsOnly>true</pickObjectsOnly> is similar, and allows only for valued objects to be clicked.

Edit: Here's an example of the idea I mentioned before, of swapping the children back and forth between clickable and non-clickable forms using PlayerHUD; it requires ConfigWindow to test (among various other features I've been working on, note the use of clipmasks and reduced number of actual defined panels):

Link to comment
Share on other sites

  • 1 month later...
Guest CommanderSirow

There is probably no chance to do that on an existing widget (eg. the games default ones) due to the "display" panel needing <TransparentInput>false</TransparentInput> in the first place? :-/

Hope the allods dev's might add a lua trigger for this :-/

Quick off-topic question: Is there a way to extract the default interface code? I know I can just open the *.pak files with any ZIP-tool, but I could not find any lua files.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

By using our site you agree to the Terms of Use