---
title: "CUEunits"
canonical: "https://docs.cuesystem.com/space/CVCIDE/503906543/CUEunits"
format: markdown
---
> Macro (toc)

---

# Context menu

If you activate the context menu above the CUEunit, the following items will be displayed:

### Events

This context menu item displays a list of events offered by a specific unit.

![image](media://c34828e0-6e83-487d-a33e-39ac0e680430)


If you click on a specific event, the source code editor opens with a predefined skeleton of the process or function. Here you can create or edit the process or function directly.

![image](media://09af06a0-3b32-4c54-9157-b873e9ef466e)

### Plugins

This context menu item displays a list of plugins offered by a specific unit.

![image](media://d52dd760-8d77-4032-9d8f-40f3efa827d4)

### GoTo Admin Web

This item is used to open the default web browser and open the Admin Web of that unit.

### Copy

This action copies the selected CUEunit on the clipboard.

### Paste

This action inserts CUEunit that you have copied to the clipboard into the MyProject Instances.

### Paste Special

This action inserts CUEunit that you have copied to the clipboard into the MyProject Instances and keeps the base part of the name.

### Delete

This action deletes the selected CUEunit.

### Properties

This action shows the properties of the selected CUEunit.

# Modules

This section contains all modules with source code.

The user module can be exported to a file .cvcm and then imported to another project.

# Applets

This section contains instances of applets used in the unit.

# Windows

This section contains the windows used in the unit. It is only active for units with graphical output, typically touch panels.

# Commands

This section contains the commands that can be used in the unit. These are commands that are not tied to channels (control ports).

# Channels

This section contains the commands for the individual channels (control ports) offered by the unit.

# Filestorage

Every CUEunit (touch panel or controller) can use files stored in the Filestorage section. Files can be created in CVC and then can be downloaded to CUEunit. All files created in CVC are part of the project file (*.CVCP).

File Types

- _VarFile stores different types of variables in binary form.
- _TextFile stores text in a readable form.

### Create and Delete Files

It is possible to create, edit and delete files of both types described above using the context menu - see picture.

If you check **Upload with Application**, the file is automatically uploaded to the Filestorage section of the hardware unit while Debug or Final Upload. File changes made during simulation or changes made in real CUEunit are not copied back to the CVC project.

### _VarFile Editing

It is possible to add a variable (at the end of the file) and delete a variable.

Every variable has a type and its value is editable. Every variable may have a Comment.

### _TextFile Editing

CVC allows simple edit functions (Ctrl+A, Ctrl+X, Ctrl+C, Ctrl+V, Del). Text can be pasted from another application via clipboard.

### Import

Now it is possible to import Var File and Binary File to the Filestorage section of any CUEunit. Var File is typically a file exported from CUEunit and created during simulation. Binary Files can be used for any type of file, e.g. pictures.

### Creating and in-place editing of _ASCIIFile files in the project file

_BinaryFile files used for raw binary data transfer, e.g. FTP Client device driver  
Automatic upload of _ASCIIFile and _BinaryFile files together with the application

### Explore Temporary Filestorage

In previous CVC versions, it was difficult to look for files stored in filestorage during the CUEunit simulation. Now it is solved.

Every running CVC instance creates temporary folders where CUEunit filestorages are located during project simulation. If you open the context menu in the CVC / CUEunit Instance / Filestorage section, you see the line Explore Temporary Filestorage of Simulated CUEunit. By clicking Windows Explorer is started in the filestorage folder.

# Webstorage

This is the place to store files of the application website.