Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display in original order #61

Open
Pastque opened this issue Nov 8, 2024 · 2 comments
Open

Display in original order #61

Pastque opened this issue Nov 8, 2024 · 2 comments
Labels
not-planned Not planned as of now

Comments

@Pastque
Copy link

Pastque commented Nov 8, 2024

Is it possible to add a list that is sorted in its original order, alternating from time to time in the script "const class const class ", for example,

const EVENT_CARD_END: StringName = "Event_Card_End_Class"
class Event_Card_End_Class extends ecs_event:
	func _init(c_battle, card):
		_data = {
			"c_battle": c_battle,
			"card": card,
		}


const EVENT_UNIT_DEATH: StringName = "Event_Unit_Death_Class"
class Event_Unit_Death_Class extends ecs_event:
	func _init(c_battle, unit):
		_data = {
			"c_battle": c_battle,
			"unit": unit,
		}

Thank you the plugin is really great.
It would be much clearer if we could choose to display the list in its original order.

@Maran23
Copy link
Owner

Maran23 commented Nov 25, 2024

Not possible and not planned for now. To support something like that, the whole logic must be refactored (right now every different type is in fact saved in an own type specific array).

@Pastque
Copy link
Author

Pastque commented Nov 26, 2024

Not possible and not planned for now. To support something like that, the whole logic must be refactored (right now every different type is in fact saved in an own type specific array).不可能,暂时没有计划。为了支持类似的东西,必须重构整个逻辑(现在每个不同的类型实际上都保存在自己的特定类型数组中)。

Thanks for the serious reply on the feasibility of the idea, very much understand the engineering complexity mentioned, in any case this plugin greatly improves the experience. Looking forward to being part of the engine directly in the future.

@Maran23 Maran23 added the not-planned Not planned as of now label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-planned Not planned as of now
Projects
None yet
Development

No branches or pull requests

2 participants