File:Screenshot of the software tool Klik & Play.png

Original file (365 × 273 pixels, file size: 55 KB, MIME type: image/png)

Summary

edit
Media data and Non-free use rationale
Description Screenshot of the 1994 software tool Klik & Play's event editor. The image is used for critical commentary on and visual illustration of the core functional component of the Klick & Play software: the Event Editor. As the primary interface for creating game logic without programming, the Event Editor is the most significant innovation of the software.
Author or
copyright owner
Clickteam
Source (WP:NFCC#4) Original publication: Software

Immediate source: Software

Date of publication 1994
Use in article (WP:NFCC#7) Clickteam
Purpose of use in article (WP:NFCC#8) The image is used for critical commentary on and visual illustration of the core functional component of the Klick & Play software: the Event Editor. As the primary interface for creating game logic without programming, the Event Editor is the most significant innovation of the software.
Not replaceable with
free media because
(WP:NFCC#1)
Its use is purely for educational and illustrative purposes, and no free equivalent can be created to authentically represent this historical software interface.
Minimal use (WP:NFCC#3) Low resolution and quality. Will only be used in one of part of the article
Respect for
commercial opportunities
(WP:NFCC#2)
The software is from 1994 and is obsolete.
Fair useFair use of copyrighted material in the context of Clickteam//en.wikipedia.org/wiki/File:Screenshot_of_the_software_tool_Klik_%26_Play.pngtrue

Licensing

edit

File history

Click on a date/time to view the file as it appeared at that time.

Date/TimeThumbnailDimensionsUserComment
current00:05, 9 August 2025Thumbnail for version as of 00:05, 9 August 2025365 × 273 (55 KB)DatBot (talk | contribs)Reduce size of non-free image (BOT - disable)
20:52, 7 August 2025No thumbnail640 × 480 (13 KB)Source555 (talk | contribs)Uploading a non-free file using File Upload Wizard

The following page uses this file: