martinhowarth / shimmer Goto Github PK

This is a possible solution for #39. Some overlap with the z based event system issue as well.

This box has a focusable attribute. Only one box can be focused at once, and there is a global stack of focused ordering (e.g. one with current focus disappears, so the next one down gets focus automatically).

One way to take focus is by clicking on the box - c.f. overlapping windows.

Possible effects:

• makes focused thing appear on top (high visual z index)

• For any mouse event within the box, only it and it's children are allowed to handle them

• need special case for drag event? Because can drag off the box, c.f. special handling in drag anchor

• the focus box and its children get first dibs on keyboard events, but do not capture all of them

• need to consider whether the children event handlers are removed from the global director event system if they are part of a focus group. This would stop them being called twice if the focus box handles passing the events down??

Currently the MouseBox calls the defined methods and always returns True if there was one defined.

Could make it so that user functions can return None (as current) or True/False to determine whether to consume the event, or let it continue.

Default should be to consume it (i.e. if return None, treat that as a return True)

We have dialogs that give a pop up window with a question. That triggers a callback on answer. It would be good to present a simple synchronous way to do this so people can get started very simply without messing with callbacks.

e.g. snap to grid

Current implementation is just a toy. now that we have a decent front end, make the backend better.

Performance enhancement.

Something to keep track of box positions and search through them to find which to send mouse events to.

Should be straightforward to add something simple here; but I think the interface for dynamically changing the size of Boxes isn't great right now so this is larger than it first appears as we should make that better too.

• Snazzy example of how to use this library
• Pictures/gifs of examples
• Links to wiki
• Links to how to use poetry
• how to get involved / contribute
• flag that this is a very new project

Simple wrapper to attach / remove a speech bubble (a TextBox) to a CocosNode.

Triggers to remove the bubble:

• time passed
• X pressed
• Keyboard input

With anchor on either cursor or on target.

Needs #40 to work with multiple layouts at once

Requires pop up boxes to be implemented first

Think this is easy for the visual elements - just ask Cocos to change z index.

However, events handlers are called in reverse order they were added, so need to fix that - Cocos doesn't seem to provide that behaviour natively.

In InstructionDisplay we blat over the methods - we should make it call both the original method (if any) and the extra mask methods:

        self.instruction.on_execute_start = self.show_mask
        self.instruction.on_execute_complete = self.hide_mask

Builds on #47

Seems like fun to make!

Need to identify key constraints that make the system interesting. e.g.

• warehouse capacity
• cargo capacity
• cargo speed

features:

• custom restrictions on what gets stored where
• custom restrictions on what can carry which cargo
• custom priorities for certain tasks

Thoughts:

• might tie into a wider "task" system for a set of workers.
• have to account for loss of sources/sinks with in-transit cargo.
• have to account for pending deliveries to prevent (or minimise, doesn't have to be exact) double delivery.

Should just be a case of defining a pytest test gatherer that detects if the run_gui fixture is being used.

E.g. for speech bubbles

Requires pop ups to be added first

Draggable and has a close button.

Currently Boxes register for many events, even if they don't implement them all - this will impact perf.

Easy option is to add a "freeze definition" option which disables handlers Which aren't used in the definition. Probably not worth supporting dynamic updates of definitions to automatically change handlers, though could be s future enhancement.

e.g. to stop something being dragged outside of a defined area.

Also make CI publish automatically on tags

Needs consistent interface for layouts. E.g width, height

Cocos2d sends events to children based on reverse order they were added. This works, but isn't intuitive when compared to the drawing mechanism of having z layers.

This should probably turn into a PR to cocos2d.

Can't test what they look like; but can test that they respond to mouse / keyboard events correctly.

Probably want some way to record mouse events from a manual run to use as input for an automated on to make it easier to define them.

With anchor on either cursor or on target.

Should split into more issues once I know what is needed, but something like:

• a key mapping options menu
• able to define callback to happens on key press/release

Examples / supported use cases

• Easy way / example to make that control a character / vehicle
• moving between buttons in a multi choice buttons widget - which is kinda a menu

Font already exists, just got to add it to ButtonDefinition and use it in Button

Might be able to import this from somewhere else?

Just an easy way to attach a draggable anchor to something

Difficultly here is dealing with the async sleeps. Think it's resolvable by just seeing a global pause timer and re-sleeping for however long has passed.

Think that pause timer needs to be a time series, with method to calculate seconds paused since X. That makes it easy to determine how long to re-sleep for

Needs:

• SelectionAnchor - a box of zero or any size that can be attached to any other box
• drag and release selection box, which returns list of selection anchors that it overlaps

This is a box Grid that arranges boxes while accounting for their size. The current basic one just has a specified number of boxes per row which only looks good for boxes of the same size.

Want an arrangement which takes fixed width or height in pixels (the other implicit is infinite) and fills in as many boxes as possible per row/column while respecting spacing. Should also handle justifying to edges (right/centre/left/bottom/top) leaving extra space as needed so you end up with a nice square grid.

There isn't anything special about a background - shouldn't be in the base class.

I'm imagining a thin red outline for every Box.rect currently in the scene to aid debugging of visual layouts.

This might possibly get too cluttered for many Boxes / overlapping boxes.

Possible extension is to show/hide the outlines on hover - this helps distinguish boxes that aren't an exact overlap.