When you write "I have a docker-compose file" you probably mean you have a compose file, which is equally probably named docker-compose.yaml or docker-compose.yml.
Having said this, Docker Desktop is made of many components, the deamon, the notary, a cli client, a gui dashboard, ... which, all together, constitutes the Docker Desktop ecosystem.
Running a compose file using Docker Desktop is running it inside this ecosystem, not in a particolar tool.
For instance I downloaded an awesome compose file and executed it inside Docker Desktop using the experimental (terminal-based) tool "docker compose"

once the services are up, I was able to manage the "compose" within the dashboard that is another tool part of Docker Desktop

here I can stop the compose and be able to hit the START button, being able to run the compose from a Docker Destop (gui) component that is not a terminal-based tool.

For the sake of completeness docker-compose file was originally the cli implementing originally the command to manage compose file without being in swarm mode. It is still available and used in systems where Docker Desktop is not available, e.g. raspbian.