Suggestion Issue: Clear list/map attribute on behaviors tab


Pages: 1

Luyren

  • Master Stencyler
  • *
June 29, 2019, 12:24:29 pm
A button to remove all items from a list or map on the behaviors tab of an actor or scene.

I use one behavior to manage cutscenes in my projects, and a list handles the order in which they happen. I make the entire cutscene in a .txt file and import that into the list. A lot of times it's easier to make changes to the .txt file and reimport it, specially when I have to change several items from the list, but I have to manually remove every item before I can do that.  The same process happens for menus (100+ items on the list) and databases in my games.

Having a button to quickly remove all items would be really helpful.
« Last Edit: June 29, 2019, 12:25:59 pm by Luyren »


LIBERADO

  • Expert Stencyler
  • *
June 29, 2019, 07:21:38 pm
+1

This is a good idea, as well as a button to remove all unused attributes.


Justin

  • Master Stencyler
  • *
June 29, 2019, 07:32:47 pm
Can you explain what you mean by that, LIBERADO?


LIBERADO

  • Expert Stencyler
  • *
June 29, 2019, 07:51:54 pm
I mean a button or menu option to remove all created local attributes that are no longer necessary because they are not being used in any event.
« Last Edit: June 29, 2019, 08:02:05 pm by LIBERADO »


Justin

  • Master Stencyler
  • *
June 29, 2019, 08:15:31 pm
Okay, I thought that's what you meant. I'm just not sure why you're mentioning that in this issue, since it seems pretty different. Could you make a new issue for that?


LIBERADO

  • Expert Stencyler
  • *
June 30, 2019, 04:38:05 am
After agreeing with the Luyren suggestion, I have impulsively mentioned my idea very briefly because it also has to do with removing all elemets of something.

But yes, I should make a new issue for it, and I will do.   


dtishin

  • Subscriber - Stencyl Indie
  • *
May 29, 2020, 05:31:10 pm
I mean a button or menu option to remove all created local attributes that are no longer necessary because they are not being used in any event.

Great idea, and something I badly need for my project. But how are you planning to make sure that the local attribute is not being referenced in the code any more?

It's possible to refer to attributes by block "For actor, get attribute" - which basically uses two free-form textfields for calling both the behaviour and its attribute. And this of course means that I can fill in these text fields procedurally after compilation - which will not be caught by your suggested "sweeper" utility...


Pages: 1

Details

  • Reported
    June 29, 2019, 12:24:29 pm
  • Updated
    May 29, 2020, 05:31:10 pm

  • View Status
    Public
  • Type
    Suggestion
  • Status
    New
  • Priority
    Normal
  • Version
    3.5.0 beta 1
  • Fixed in
    (none)
  • Assigned to
    (none)
  • Category
    Behavior Settings

Tags