{"id":4834,"date":"2024-05-03T18:37:39","date_gmt":"2024-05-03T18:37:39","guid":{"rendered":"https:\/\/castle-engine.io\/wp\/?p=4834"},"modified":"2024-05-03T18:37:39","modified_gmt":"2024-05-03T18:37:39","slug":"find-ctrl-f-find-next-f3-to-easily-find-components-by-name-useful-in-large-designs","status":"publish","type":"post","link":"https:\/\/castle-engine.io\/wp\/2024\/05\/03\/find-ctrl-f-find-next-f3-to-easily-find-components-by-name-useful-in-large-designs\/","title":{"rendered":"Find (Ctrl+ F) \/ Find Next (F3) to easily find components by name (useful in large designs)"},"content":{"rendered":"
\n \"Find<\/a><\/td><\/tr><\/table>\n

A new feature, small but invaluable, for navigating large designs in our editor<\/a>: easily find component by name.<\/p>\n

    \n
  1. Use editor menu item “Edit -> Find”<\/em> (Ctrl + F<\/em>) to see a text box where you can type component name.<\/p>\n<\/li>\n
  2. \n

    Typing anything there, like camera<\/code>, will search and select the first component matching given name (as a substring, ignoring case, so e.g. it will find MyCamera1<\/code>).<\/p>\n<\/li>\n

  3. \n

    Pressing F3<\/em> (or using menu item “Edit -> Find Next”<\/em>) searches for next occurrence.<\/p>\n<\/li>\n

  4. \n

    Just press Ctrl + F<\/em> again to hide the search bar. Or leave it be — you can just ignore it and keep working, it will not change your selection unless you explicitly type something into the search bar or press F3<\/em>.<\/p>\n<\/li>\n<\/ol>\n

    This allows to move around in a larger designs much easier. An example is the platformer example<\/a> – see “play” game design.<\/p>\n

    We have another feature planned to streamline working in large designs: easily hide behaviors<\/a> or non-visual components (like fonts). By default, our component hierarchy may seem “deeper” than in other game engines because our hierarchy by default contains also behaviors (which in e.g. Unity are delegated to the object inspector). This has some benefits (for both code, and editor copy-pasting, our “behaviors” are just regular components, you can create\/copy-paste\/drag then just like e.g. TCastleTransform<\/code> components; they also have names). But the downside is that our hierarchy tree looks “deeper”. We plan to have checkboxes to just easily hide this complication and\/or move it to the right sidebar.<\/p>\n

    Do you like what we do? Please support us on Patreon<\/a>!<\/p>\n","protected":false},"excerpt":{"rendered":"

    A new feature, small but invaluable, for navigating large designs in our editor: easily find component by name. Use editor menu item “Edit -> Find” (Ctrl + F) to see a text box where you can type component name. Typing anything there, like camera, will search and select the first component matching given name (as … <\/p>\n

    Continue reading \u27a4 “Find (Ctrl+ F) \/ Find Next (F3) to easily find components by name (useful in large designs)”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":4835,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"publish_to_discourse":"1","publish_post_category":"9","wpdc_auto_publish_overridden":"","wpdc_topic_tags":"","wpdc_pin_topic":"","wpdc_pin_until":"","discourse_post_id":"4513","discourse_permalink":"https:\/\/forum.castle-engine.io\/t\/find-ctrl-f-find-next-f3-to-easily-find-components-by-name-useful-in-large-designs\/1175","wpdc_publishing_response":"","wpdc_publishing_error":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[1],"tags":[],"class_list":["post-4834","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/castle-engine.io\/wp\/wp-content\/uploads\/2024\/05\/editor_find.png","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p9IgYW-1fY","jetpack_likes_enabled":false,"_links":{"self":[{"href":"https:\/\/castle-engine.io\/wp\/wp-json\/wp\/v2\/posts\/4834","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/castle-engine.io\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/castle-engine.io\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/castle-engine.io\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/castle-engine.io\/wp\/wp-json\/wp\/v2\/comments?post=4834"}],"version-history":[{"count":6,"href":"https:\/\/castle-engine.io\/wp\/wp-json\/wp\/v2\/posts\/4834\/revisions"}],"predecessor-version":[{"id":4841,"href":"https:\/\/castle-engine.io\/wp\/wp-json\/wp\/v2\/posts\/4834\/revisions\/4841"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/castle-engine.io\/wp\/wp-json\/wp\/v2\/media\/4835"}],"wp:attachment":[{"href":"https:\/\/castle-engine.io\/wp\/wp-json\/wp\/v2\/media?parent=4834"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/castle-engine.io\/wp\/wp-json\/wp\/v2\/categories?post=4834"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/castle-engine.io\/wp\/wp-json\/wp\/v2\/tags?post=4834"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}