Giter Site home page Giter Site logo

tilda's Issues

Inspector elements should load faster

... currently slowing down the workflow too much.
Is there a way to speed this up?
Can they be kept invisible for clips that have been inspected already?

Change Color System for Clips

Currently colors are being computed in place (Forms Editor, Copy/Paste ... whenever a category can be introduced).

TODO:

  • Wrap computation and assignment of colors, ideally automatically inside TildaCore whenever a new Category is introduced in the Dictionary
  • Check out Pastel Color Pallette to avoid bleeding eyes

Changeble size of Variable TextBox

Sometimes variable is too big to fit into small line of text as it is now. It would be nice to have textbox, that changes depending on the text size

Speed up Undo with Redis

I think this can be achieved with just storing a list of Guids of the objects that have been affected by the last get / set / create / delete clip operations. If you have that, you can set the state for these objects in redis precisely, without always pushing the whole timeline

Edit Clip UI: unit of duration

It's not clear out of the box what unit (seconds/frames) the duration is expecting in the edit clip UI. Also using Backspace in the value field for duration has a weird behaviour

Follow vvvv pack folder-structure convention

Hi,
/modules and /vl should be moved as subfolders to a new /nodes/ folder so vvvv will pick those nodes up correctly and show them in the nodebrowser.

Less important, but still note-worthy: I'd propose to keep the root folder as empty as possible, considering "Tilda Example Patch.v4p" a girlpower/example patch and moving it there as well (+ the demo Tilda-Example-Timeline.xml)

Johannes

Clip events observers doesn't work properly

When I try to observe events for multiple clips, e.g. removal or creation of more than one clip, observers doesn't do shit. For more than one clip I start getting observables only on my second action.

If I do changes for only one clip everything works as expected without that weird repeatition of action to register changes.

StackExchange.Redis.RedisConnectionException

When trying to connect:

StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(s). InternalFailure (None, last-recv: 3506) on localhost:6379/Interactive, Idle/Faulted, last: ECHO, origin: ReadFromPipe, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 60s, state: ConnectedEstablished, mgr: 9 of 10 available, in: 0, in-pipe: 3506, out-pipe: 0, last-heartbeat: never, global: 106s ago, v: 2.0.601.3402
at StackExchange.Redis.ConnectionMultiplexer.ConnectImpl(Object configuration, TextWriter log)
at Tilda.Sync.TClient.Connect(String& Status, String options)

Inspector: Changing and reverting value of field doesn't trigger change

When opening the clip menu and changing the value of a field, the change is immediately applied to the clip as expected. However, when reverting that change to its original value (say changing the duration from 100 to 200 and back to 100) does not effect a change since the field is not marked as changed by windows forms. Same behaviour for categories.

Make editing of Keyframe Clips safer

Right now there are too many wrong clicks that break the user interaction workflow.
Put Editing into its own editing state like for envelope clips, or rather make a global editing state, that can hold an argument as of which clip type is being edited.

At the same time, make sure that not too many clicks are necessary to change values of keyframes. Maybe just keep a modifier key pressed to focus editing only on keyframes (alt isn't used right now in this instance)

Rework automata logic

The current automata implementation is suboptimal. Editing the graph is not convenient. Are there better solutions to this?

Envelope values are only evaluated when clip alpha is 1

Hello,

As explained in the title, clip values cant be animated until clip fade in/out is equal to 1.

Wouldn't it make more sense to allow animation as soon as value is over 0? (or to have an option to define that behaviour)

curve

Thanks

Bezier envelope evaluation returns incorrect results

Hello, as shown in the screenshot, bezier interpolation for envelopes provides incorrect values.

As the timer is trough the point (highlighted in the xml), we should expect an equivalent return value from the node in vvvv.

bezier

Thanks

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.