Aron 

1. Ninext console hiding table tools

Yes, this issue is already known by the Ninox team. They are currently working on a fix so that the console can remain open without blocking access to the table tools during development.

In the meantime, you can install the classic version of Ninext, which does not have this behavior:
https://docs.ninext.fr/classic-installation-50

1. Uninstalling plugins and impact on the database schema

When you uninstall Ninext, the database schema (tables, fields, relations) is not removed or structurally modified. Your data remains intact.

However, you will lose all features injected by Ninext, including:

• Badges on files, tabs, and buttons

• Interception of onclick events on fields and views

• Modules related to custom events (viewEvent, buttonEvent, etc.)

• JavaScript calls using the #{ ... }# syntax

The most critical point concerns these JavaScript calls:
if your application relies on them for essential logic (calculations, automations, specific interactions), those parts will stop working after uninstallation.

Additionally, some workspace-related settings will also be lost, such as:

• The field selected during the last session

• Filters defined in Code Finder

• Custom representations created in the Schema tab

These elements do not affect your data, but they may impact your development workflow and organization.

The Ninox warning message is therefore preventive: it indicates that a plugin may affect functionality, without specifying exactly what. Before uninstalling, it is recommended to check whether your application uses #{...}# calls, extended events, or important interface customizations.

1. Field copy-paste functionality

Thank you 😊
Yes, this feature really makes life easier. Many of us truly appreciate it!