I would like to suggest adding a built-in tooltip property for items in prototypes.

Feature description:

- Allow designers to assign tooltip text to items directly within Lunacy.

- Tooltips should appear during prototype preview without manually creating and positioning tooltip designs.

- Should support basic customization (e.g., delay, position, style) while keeping default design for convenience.

Why this is important:

- Currently, designers have to manually create tooltip components and manage their visibility in prototypes.

- A native tooltip property would simplify workflows, save time, and make prototypes cleaner and more interactive.

- Common use case in UI/UX design for hints, explanations, or hover effects.

Example use cases:

- Buttons with explanatory tooltips

- Icons with short descriptions

- Interactive UI elements needing contextual hints

This feature would greatly improve prototyping efficiency and UX fidelity.

Thank you for considering this enhancement!

This would be especially useful for UI components like buttons, panels, and dialog backgrounds, improving workflow and preventing visual distortion.

(it may be also called Sub-Region(?))

https://lunatics.icons8.com/discussion/740/portable-version/

I encountered a performance issue when working with a large number of components in a project.

Steps to Reproduce:

1. Create or open a project containing thousands of components (e.g., several thousand icons).

2. Try to search for a component or replace a component via the component search dropdown.

3. Click on the search box or attempt to select a component.

4. The application becomes unresponsive for several seconds as it tries to load all components at once.

Expected Behavior:

- The component search and replacement should remain responsive, even with thousands of components.

- Components can be loaded progressively or lazily to avoid freezing the application.

Actual Behavior:

- The application hangs or is not responsive for several seconds.

- Workflow is interrupted, making large files difficult to manage.

- Other design tools handle this smoothly by progressively loading components without freezing.

Impact:

- Major disruption in large projects or design systems.

- Slowdowns reduce productivity and may force users to split files unnecessarily.

- Critical for users managing icon libraries, UI kits, or design systems with many components.

Additional notes:

- Issue occurs consistently with large component sets.

Thank you for investigating this performance problem.

but could you add an option for free personal use? so e.g.: that I have the ability to host lunacy-dedicated/"lunacyapp.com" locally for my family

would this be Possible?

I found an issue where copying components or frames between projects can cause some prototype settings to be lost.

Steps to Reproduce:

1. Open Project A containing components with prototype interactions (e.g., links, state changes, hover effects).

2. Select one or more components or frames.

3. Copy (Cmd/Ctrl + C) and paste (Cmd/Ctrl + V) into Project B.

4. Observe that some prototype settings or interactions do not carry over to the new project.

Expected Behavior:

- All prototype settings, interactions, and states should be preserved when copying components between projects.

- Copied components should behave identically in the new project as in the original.

Actual Behavior:

- Certain prototype interactions are lost after pasting.

- The user must manually restore prototype settings in the new project.

Impact:

- Interrupts workflow, especially in large design systems.

- Time-consuming and error-prone for designers reusing components across projects.

- Reduces reliability of component reuse in prototypes.

Additional notes:

- The issue occurs consistently when copying multiple components with interactions.

Thank you for investigating this issue.

I would like to suggest adding a multi rename (bulk rename) feature for layers and frames.

Feature description:

Allow users to select multiple layers or frames and rename them all at once using a dedicated rename dialog.

Suggested behavior:

- Select multiple items

- Press:

 - Cmd + R (Mac)

 - Ctrl + R (Windows)

- A modal opens with the following options:

 - Find & replace text

 - Add prefix

 - Add suffix

 - Insert sequential numbers (ascending or descending)

Why this is important:

Renaming layers manually is time-consuming, especially in large files with many frames, icons, or repeated elements.  

This feature already exists in tools like Figma and significantly improves workflow speed and file organization.

Use cases:

- Renaming icon sets

- Numbering frames or screens

- Adding consistent prefixes (e.g., "btn_", "icon_", "card_")

- Cleaning up layer names before handoff to developers

This would be a huge productivity boost for everyday design work.

Thank you for considering this feature!

I would like to suggest a small but highly useful navigation feature for prototype preview.

Feature description:

- When viewing a prototype, allow the user to quickly jump to the corresponding design location in the editor

- Could be a button or shortcut like “Go to design” that centers the view on the selected frame/artboard

Why this is important:

- In large files with many frames or screens, it can be time-consuming to find the original design in the editor

- Designers often want to inspect or edit a specific frame while testing the prototype

- This feature would improve workflow efficiency and reduce frustration

Example use cases:

- Quickly navigating to a frame after testing an interaction

- Inspecting design details without manually scrolling through large artboards

- Editing content while previewing user flows

This small addition would greatly improve navigation and speed when working with prototypes.  

Thank you for considering this improvement!

I would like to report a component behavior that could be improved to better match workflows in other design tools.

Current behavior:

When the main (parent) component is deleted, all of its child instances become detached and lose their connection completely.

Expected / suggested behavior:

- Child instances should not automatically detach when the main component is deleted.

- It should be possible to restore or recreate the main component from one of the existing child instances.

- Alternatively, deleting the parent should keep the children as instances, not independent detached elements.

Why this matters:

In real projects, it is easy to accidentally delete a main component. In other design tools, designers can recover the component from its children without losing structure and overrides.  

The current behavior makes recovery impossible and can result in significant rework.

Use case:

- Large design systems with many component instances

- Accidental deletion of a main component

- Safer, non-destructive component workflows

Thank you for considering this improvement!

I encountered an issue where changing a component state in a prototype unexpectedly modifies the design in the editor.

Steps to Reproduce:

1. Open a design file with a component that has multiple states.

2. Enter prototype preview.

3. Switch the component to a different state within the prototype.

4. Exit prototype preview and return to the design editor.

5. Observe that the component's state change from the prototype has been applied to the design.

6. The issue temporarily resolves by closing and reopening Lunacy.

Expected Behavior:

- Changes made to component states in prototype preview should not automatically modify the design.

- Prototype interactions should remain separate from the design unless explicitly applied.

Actual Behavior:

- Component states changed in the prototype are applied to the design unexpectedly.

- Only reopening the application resets the display to the correct state.

Impact:

- Can cause confusion and accidental design modifications.

- Risk of unintentionally altering master components.

- Interrupts workflow when testing interactions in prototypes.

Additional notes:

- Issue occurs intermittently but is reproducible with components having multiple states.

- OS / Lunacy version info can help with debugging.

Thank you for investigating this issue.

I encountered a crash issue related to component states.

Steps to Reproduce:

1. Open a design file with a component that has multiple states.

2. Select the component.

3. Attempt to switch its state (e.g., from "default" to "hover" or "active").

4. The application crashes immediately and closes.

Expected Behavior:

- The component state should change without causing the program to crash.

- The user should be able to switch between states safely.

Actual Behavior:

- Lunacy crashes upon changing the component state.

- Any unsaved work is lost.

Impact:

- Significant disruption to workflow.

- Risk of losing unsaved design work.

- Prevents testing or demonstrating interactive components.

Additional notes:

- The crash occurs intermittently but is reproducible on components with multiple states.

- File type: .lunacy (or similar)

- OS: Windows 10

Thank you for looking into this issue.

I encountered an issue with the style search box in the editor.

Steps to Reproduce:

1. Open a design file.

2. Select an object.

3. Open the style dropdown (e.g., text style, color style).

4. Click on the search box and start typing the name of a style.

5. After typing one or more letters, the search box loses focus and typing stops.

Expected Behavior:

- The search box should retain focus while typing.

- Users should be able to type the full style name without interruption.

- Search results should update in real-time as expected.

Actual Behavior:

- The search box unexpectedly loses focus after typing some characters.

- The user has to click again to continue typing.

- Searching for styles becomes cumbersome.

Impact:

- Slows down workflow, especially in files with many styles.

- Frustrates users during repetitive tasks like applying text or color styles.

Thank you for investigating this issue.

I encountered an intermittent issue where variables do not always display correctly in the editor.

Steps to Reproduce:

1. Open a design file that uses variables.

2. Observe the variable panel or variable options in properties.

3. Sometimes, variables are not visible.

4. Closing and reopening Lunacy may temporarily fix the issue, but the problem can reoccur.

Expected Behavior:

- Variables should always be displayed in the editor consistently.

- Users should have reliable access to all defined variables without restarting the application.

Actual Behavior:

- Variables sometimes disappear from the editor.

- The issue is intermittent and unpredictable.

Impact:

- Interrupts workflow and causes confusion.

- May lead to mistakes if variables are assumed to be unavailable.

- Reduces reliability of variable-based design systems.

Thank you for looking into this issue.

I made a small rectangular graphic to put text over, made a text area the same size as my graphic and added text. I notice that after typing two lines of text the top line extends outside the area I selected with both 'top align' and 'center align' options.

However, a single line of text seems to stay with the set area

the addition of feature to add physical length as international unit or metric will be simple but strongly useful. it can help designer with printing media to design more intuitive and accurate, they can insert length accurately as their paper, magazine, and such banner.

First of all, a huge compliment on what you're doing! I love this program and use it regularly at work and in my personal life.

One feature I'd really like to see added is the ability to modify the size of arrowheads.

Being able to choose between different arrowheads is already very useful, but being able to make them even larger and smaller would be fantastic.

So far, I've been crafting the arrows myself using different shapes, but having this feature integrated would save a lot of time.

Of course, this is just a cosmetic change, but perhaps you could consider it.

Anyway, have a great day and thank you for your fantastic project!

 maybe bc i don't use Figma.

also, some stuff I like don't have shortcuts and i want them? so hope if there any plan to add them.

Sure I may miss a few plugins here and there but I really don't miss any to the point where I can't use Lunacy. Although a plugin architecture would definitely help uptake IMHO. :)

I would absolutely love to see Lunacy be able to export websites that I prototype in pure, accurate HTML and CSS across the desktop, tablet and mobile breakpoints.

Currently the website creation tool landscape is pretty bleak if you're on a MAC or Linux (I use both - actually I'm in the process of moving to Linux and Lunacy has made the move so much more comfortable)

So, Export to HTML and CSS, maintain a folder structure, browser preview. I don't even need built-in FTP or anything like that so long as Lunacy can accurately export my websites in HTML and CSS I'd be a really happy camper!

Thanks for a great open source product!!! 🙏

I trust this message finds you well. I am reaching out to highlight a feature request regarding the handling of CMYK colors in the Lunacy app. Currently, the application primarily focuses on RGB color representation, and I believe incorporating robust CMYK support would significantly enhance its utility for users in graphic design and print-related workflows.

Feature Request Description:

The Lunacy app currently excels in providing a user-friendly platform for graphic design. However, the absence of comprehensive support for CMYK color spaces limits its effectiveness for professionals working on print projects. My suggestion is to introduce enhanced CMYK color features to broaden the application's capabilities.

• Lunacy App Version: 9.3.1.4
• Operating System: windows 10

Sorry GIF is so bad. Gave up from strict upload limit and obtuse 413 code which apparently means its too big but it can't give you any useful error message.

I did my best to communicate the tools I need in Lunacy which is basically how any Adobe product does it.

• I'm using beta12.0.0.18481 now and i can't use IME to type Chinese

• By the way, I'd like to know if there is a Chinese user group, and I'd be very happy. thx:)

It seems the glyph outline and shadow are rendered without applying OpenType features.

I mostly tested on Arabic as I'm more familiar with it, some features like fina, init, medi, rlig/liga are respected. Other features are ignored and rendered in default positions.

Here's is what Lunacy currently rendered, the primary text in black displayed the font correctly while the in white outline, only RTL text misaligned, the Latin text (e.g. A + ̆) displayed correctly.

Here's the same text with partially Opentype features displayed in font testing website that use Harfbuzz (Crowbar)

And with the features turned on:

Font used:

IBM Plex Arabic (Google Fonts)

The Year of Camel

JAWI Diwani

Test text:

Ă Ŭ ŏ ŭ ê رَ نِيسْکَالاَ اٴيرَاهَا

چمڤدق

לוּנֶסִי لُونٚسِي

Currently, you can’t drag components or styles between groups or reorder them manually. Everything is locked in a rigid list—forcing constant regrouping or perfect upfront planning. This breaks iterative design workflows.

Solution

• ✅ Drag-and-drop components & styles (within/between groups, to root)
• 🔀 Sorting options: by name, date, or custom user order🎨 Apply same logic to
• all styles (colors, text, effects)

Below are reference screenshots illustrating the current state vs. the proposed behavior:

(Note: The mockups demonstrate core functionality only and are not intended as final UI designs.)

1. Before:

2. After:

The groups were made in blue to better distinguish them from the rest of the elements.