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

Add KHR_node_hoverability #2428

Merged
merged 2 commits into from
Jul 29, 2024
Merged

Conversation

KhronosWebservices
Copy link
Member

Add KHR_node_hoverability after KHR_node_visibility

Add KHR_node_hoverability after KHR_node_visibility
Copy link
Member

@lexaknyazev lexaknyazev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The text above says:

All items are listed in alphabetical order.

Please put KHR_node_visibility after KHR_node_selectability for consistency.

@KhronosWebservices
Copy link
Member Author

A lot of this is not in alphabetical order, and that easy to fix. Wondering: the list above has EXT items after KHR items? Do we want EXT first or last? Last puts it out of alphabetical order.

@lexaknyazev
Copy link
Member

I think we agreed to sort alphabetically ignoring the prefix so that, e.g., both *texture_procedurals* entries are adjacent.

@KhronosWebservices KhronosWebservices merged commit 684e63c into main Jul 29, 2024
3 checks passed
abbaswasim pushed a commit to abbaswasim/glTF that referenced this pull request Sep 7, 2024
* Add KHR_node_hoverability
* Resort extension list
kwokcb added a commit that referenced this pull request Sep 17, 2024
* KHR_materials_ior: Minor typo: plural instead of singular (#2413)

* Update anisotropy extension spec (#2409)

* Clarify and simplify formula for attenuation. (#2414)

* Add TRACE prefix (#2417)

* Update clearcoat extension spec (#2415)

* Update README. (#2427)

* Add KHR_node_hoverability (#2428)

* Add KHR_node_hoverability
* Resort extension list

* EXT_mesh_gpu_instancing: Suggest extensionRequired usage (#2405)

* Add button/link to glTF Discord (#2429)

As there is a lot more traffic to the Khronos glTF Discord than there is to Slack, a button pointing users to Discord will be helpful.

---------

Co-authored-by: Andreas Atteneder <andreas.atteneder@unity3d.com>
Co-authored-by: Alexey Knyazev <3479527+lexaknyazev@users.noreply.github.com>
Co-authored-by: Ed Mackey <elm19087@gmail.com>
Co-authored-by: Marco Hutter <javagl@javagl.de>
Co-authored-by: Khronos Group Web Services <webservices@khronosgroup.org>
Co-authored-by: Arseny Kapoulkine <arseny.kapoulkine@gmail.com>
Co-authored-by: James Riordon <outofcontrol@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants