Image creation program and information processing apparatus

Abstract

To enable appropriately managing files of print images including data of a database together with the database.SOLUTION: An information processing apparatus creates a print image following an editing operation by a user, and displays the print image on a first area. A database can be displayed on a second area. The editing operation includes adding, to the print image, data included in the database displayed in the second area. The information processing apparatus can store the print image in a first storage format or in a second storage format. The first storage format is a format in which the print image and the database are integrated into one file to store. In a case where the database is displayed when a storage request is received, the information processing apparatus notifies the user of a fact that storing in the first storage format is available.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a technique for generating, by an information processing device, an image to be printed by a printing device. [Background technology]

[0002] Patent Document 1 discloses a program for generating templates to be printed by a label printer. This program can acquire a database and generate a template including objects linked to the database. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-211904 A Summary of the Invention [Problem to be solved by the invention]

[0004] It is expected that users will want to save the generated template as a file and later open the file to edit the template or print it on a printing device. In this case, it is desirable that the file be opened in a state where the link between the template and the database is properly maintained.

[0005] An object of one aspect of the present disclosure is to enable appropriate management of print image files including database data together with the database. [Means for solving the problem]

[0006] One aspect of the present disclosure provides an image creation program executable by an information processing device. The information processing device includes a first communication unit configured to communicate with a printing device, a display unit, an input unit, and a control unit. The control unit is capable of executing the image creation program. The image creation program causes the control unit to execute an edit screen display process, a database display process, a print image creation process, a save format acceptance process, and a notification process.

[0007] The editing screen display process displays an editing screen having a first area and a second area on a display unit. The database display process displays a database in the second area in response to a database display request for requesting display of a database.

[0008] The print image creation process creates a print image, which is an image to be printed by the printing device, in accordance with an editing operation by a user via an input unit and displays the print image in a first area. The editing operation includes adding data contained in the database displayed in the second area to the print image.

[0009] The save format receiving process receives, in response to a save request for saving a print image, a designation as to whether the print image is to be saved in the first save format or the second save format. The first storage format is a format in which the print image created in the print image creation process and the database (if the database is displayed on the editing screen when the save request is received) are integrated and saved into a single file.

[0010] The second storage format is a format in which an image information file indicating a print image created in the print image creation process is stored independently from the database. The notification process notifies the user that saving in the first saving format is possible when (i) a save request is received and (ii) a database is displayed on the edit screen when the save request is received.

[0011] According to such an image creation program, the print image file including the database data can be appropriately managed together with the database. In the first storage format, an image information file and a database file indicating the database may be generated. In the first storage format, the image information file and the database file may be integrated into one file. In another aspect of the present disclosure, an information processing device may be provided that is configured to execute the above-mentioned editing screen display process, database display process, print image creation process, and save format acceptance process. The information processing device may include the above-mentioned first communication unit, display unit, input unit, and control unit, and the control unit may be configured to execute each of the above processes. The control unit may execute each of the above processes according to a computer program. Alternatively, the control unit may realize some or all of the above processes by so-called hardwired logic (i.e., wired logic) without relying on a computer program. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a configuration diagram of a printing system according to a first embodiment. [Diagram 2] FIG. 11 is an explanatory diagram showing an editing screen in a first state. [Diagram 3] FIG. 13 is an explanatory diagram illustrating a database open dialog. [Figure 4] FIG. 13 is an explanatory diagram showing the editing screen in a second state. [Diagram 5] FIG. 13 is an explanatory diagram showing the editing screen in a third state. [Figure 6] FIG. 2 is an explanatory diagram showing a file structure. [Figure 7] FIG. 13 is an explanatory diagram showing a message window. [Figure 8] FIG. 11 is an explanatory diagram showing a file save dialog in a first state. [Figure 9] FIG. 13 is an explanatory diagram showing the file save dialog in a second state. [Figure 10] 4 is a flowchart of a main process according to the first embodiment. [Figure 11] 11 is a flowchart of a storage process according to the first embodiment. [Figure 12] 13 is a flowchart of a previous application confirmation process. [Figure 13] 13 is a flowchart of a storage process according to the second embodiment. [Figure 14] FIG. 11 is an explanatory diagram showing another example of the file save dialog. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the drawings. [1. First embodiment] (1-1) Printing system configuration 1, the printing system of the first embodiment includes an information processing device 1 and a printing device 101. The printing system further includes a server 200. The information processing device 1 is configured to be able to communicate with the printing device 101 and the server 200.

[0014] When the printing device 101 acquires a print command including image data from the information processing device 1, the printing device 101 can print an image indicated by the image data on a print medium. The printing device 101 of the first embodiment has the form of, for example, a label printer or a label writer.

[0015] That is, the print medium in the first embodiment has a long, tape-like shape. The printing device 101 is configured to print an image on the print medium along its length. The print medium on which the image is printed is cut and / or peeled off and used as a label. The label is attached to various objects, such as name tags, file spines, store price tags, mailing envelopes, industrial materials, fixtures, notebooks, signs, and other objects. Hereinafter, the entire image included in one label is referred to as the "label image."

[0016] The information processing device 1 can generate a print command and send it to the printing device 101. The information processing device 1 can execute a label image creation application 5a. The label image creation application 5a is software including a computer program for creating a label image to be printed by the printing device 101. Note that creating a label image is not limited to creating a new label image, but also includes editing an already created label image. A user of the printing system can create a label image using the label image creation application 5a on the information processing device 1.

[0017] When the information processing device 1 receives an instruction to print the created label image, it transmits image data representing the label image to the printing device 101. More specifically, the information processing device 1 of the first embodiment generates a print command including the image data, and transmits the print command to the printing device 101.

[0018] The information processing device 1 may communicate with the printing device 101 and the server 200 using any communication method. The information processing device 1 may communicate with each of the printing device 101 and the server 200, for example, wirelessly or via wired communication. Communication methods for wireless communication may include, for example, wireless LAN and Bluetooth. Note that "Bluetooth" is a registered trademark. Communication methods for wired communication may include, for example, USB (Universal Serial Bus) and wired LAN.

[0019] The server 200 has SLBX compatibility information, which will be described later. The information processing device 1 can obtain the SLBX compatibility information from the server 200 through the above communication. The server 200 may be managed by the vendor of the printing device 101, for example.

[0020] (1-2) Configuration of information processing device 1, the information processing device 1 includes a control unit 2, a display unit 3, an input unit 4, and a storage unit 5. The control unit 2 includes a CPU 2a and a memory 2b. The CPU 2a as a processor executes processing according to computer programs stored in the memory 2b and the storage unit 5. The memory 2b may include a semiconductor memory such as a ROM, a RAM, an NVRAM, or a flash memory.

[0021] The storage unit 5 includes storage such as a solid state drive (SSD) and a hard disk drive (HDD), and stores various computer programs and data. In the first embodiment, the programs stored in the storage unit 5 include an operating system (hereinafter, referred to as "OS") and a printer driver. The printer driver is software for controlling the printing device 101 from the information processing device 1.

[0022] The storage unit 5 further stores the above-mentioned label image creation application 5a. The label image creation application 5a realizes an image creation function. The image creation function includes creating a label image based on an operation of a user of the printing system, and sending a print command including image data showing the label image to the printing device 101 via the printer driver. The image creation function is realized by the control unit 2 executing the label image creation application 5a. In the first embodiment, the OS, the printer driver, and the label image creation application 5a are installed in the information processing device 1 and used.

[0023] The label image creation application 5a may have some or all of the functions of a printer driver. In other words, the label image creation application 5a may be configured to send the created image data to the printing device 101 without going through application software other than the label image creation application 5a.

[0024] In the following description, the entity that executes a program (for example, the control unit 2 in the information processing device 1) may be described simply by the program name or software name. For example, the description "the label image creation application 5a" may specifically mean "the control unit 2 that executes the label image creation application 5a."

[0025] The OS may be configured in any manner, for example, Windows (registered trademark of Microsoft Corporation), Mac OS (registered trademark of Apple Inc.), or another OS.

[0026] The label image creation application 5a is installed and used in a computer system including an OS. The OS has a file system. The file system manages various files. Details of the file system are generally well known as a function of the OS, so a description thereof will be omitted here. Note that the label image creation application 5a may be executable without being installed in the computer system.

[0027] The label image creation application 5a may be stored in any manner in the storage unit 5. For example, the label image creation application 5a may be read into the information processing device 1 from a storage medium such as a CD, a DVD, or a USB memory and stored in the storage unit 5. For another example, the label image creation application 5a may be downloaded from an external information processing device (for example, the server 200) to the information processing device 1 via a network and stored in the storage unit 5. For another example, the label image creation application 5a may be stored in advance in the storage unit 5 when the information processing device 1 is shipped.

[0028] The display unit 3 is configured to display various screens to a user of the information processing device 1. Examples of the display unit 3 include a liquid crystal display, an organic EL display, a head-up display, a head-mounted display, an aerial display, etc. Examples of the various screens include an editing screen 10 (see FIG. 2) described later.

[0029] The input unit 4 includes one or more input devices, such as a keyboard and a pointing device, for receiving an input operation from a user to the information processing device 1. Specifically, the input unit 4 may include a mouse. For example, the input unit 4 may include a touch panel. The touch panel may be arranged so as to be superimposed on the entire or almost entire area of ​​the display unit 3 where an image is displayed. When the input unit 4 includes a keyboard, the keyboard may be a so-called hardware keyboard or a so-called software keyboard (or a screen keyboard). The input unit 4 may include a non-contact input interface.

[0030] The information processing device 1 includes a first communication unit 6. The first communication unit 6 is a communication interface for communicating with the printing device 101. The information processing device 1 is configured to perform the above-mentioned wireless communication or wired communication with the printing device 101 via the first communication unit 6. The above-mentioned print command is transmitted from the first communication unit 6.

[0031] The information processing device 1 includes a second communication unit 7. The second communication unit 7 is a communication interface for communicating with the server 200. The information processing device 1 is configured to perform the above-mentioned wireless communication or wired communication with the server 200 via the second communication unit 7.

[0032] The information processing device 1 may be in the form of, for example, a stationary personal computer, or in the form of a so-called notebook computer, tablet, smartphone, or the like that is easily portable.

[0033] (1-3) Printer configuration As shown in FIG. 1, a printing device 101 includes a control unit 102, a display unit 103, an input unit 104, and a communication unit 105.

[0034] The control unit 102 includes a CPU 102a and a memory 102b. The memory 102b may include semiconductor memory such as a ROM, a RAM, an NVRAM, or a flash memory. Computer programs and data for implementing various functions of the printing device 101 are stored in a non-volatile memory (e.g., a flash memory) in the memory 102b. The CPU 102a as a processor performs overall control of the printing device 101 by executing processes according to the computer programs stored in the memory 102b.

[0035] The display unit 103 displays various information to a user who operates the printing device 101. The display unit 103 may include one or more display devices, such as a lamp or a liquid crystal display.

[0036] The input unit 104 accepts various input operations from a user. The input unit 104 may include one or more input devices, such as a push button, a keyboard, a touch panel, or the like.

[0037] The communication unit 105 is configured to perform wireless or wired communication with the first communication unit 6 of the information processing device 1. The communication unit 105 receives the print command described above. The printing unit 106 is configured to print an image on a print medium under the control of the control unit 102. When the printing device 101 receives a print command from the information processing device 1, the printing unit 106 prints a label image indicated by image data included in the print command on the print medium. The printing unit 106 prints an image using any of various printing methods such as a thermal transfer method, a thermal method, an inkjet method, and a laser method. The printing unit 106 of the first embodiment may be configured to print an image on a print medium by, for example, a thermal transfer method.

[0038] In this first embodiment, an image is printed on the front side of the print medium. An adhesive is applied to the back side of the print medium, and the adhesive is covered with a release paper. It is not essential that the print medium has an adhesive. The print medium may have any form on which a label image can be printed.

[0039] The print medium of the first embodiment is provided in the form of a roll in which the print medium is wound. The print medium is stored in a cassette (not shown). The cassette is removably attached to the printing device 101. The printing unit 106 prints a label image on the print medium while pulling the print medium out of the cassette. The portion of the print medium on which the label image is printed is discharged from an outlet (not shown) provided in the printing device 101 and cut off automatically or manually.

[0040] When the control unit 102 receives a print command via the communication unit 105, it controls the printing unit 106 to print a label image on the print medium while pulling the print medium out of the cassette. In this way, a label is created for each label image.

[0041] (1-4) Creating label images using a label image creation app After being started, when a predetermined new creation trigger occurs, the label image creation application 5a displays an editing screen 10, as exemplified in FIG. 2, on the display unit 3. The editing screen 10 is a user interface for creating a label image. The new creation trigger includes an operation or input requesting the display of the initial state of the editing screen 10. The initial state of the editing screen 10 is an editing screen 10 in a state in which no label image has been created yet. Therefore, when a new creation trigger occurs, the initial state of the editing screen 10, as exemplified in FIG. 2, is displayed.

[0042] The editing screen 10 includes a menu bar 11, a toolbar 12, and an editing area 13. The editing area 13 includes an image display area . A label object 16 is displayed in the image display area 14. In the following description, the object is referred to as "OBJ." The label object OBJ16 includes a label image OBJ16a indicating a label image, and an input frame 16b indicating an area in which the label image OBJ16a can be placed.

[0043] Label image OBJ16a virtually shows how the label image currently being created will actually be printed on the print medium, i.e., it is a preview image of the label image. Label OBJ16 is a preview image of the label image including the print medium. Label OBJ16 shows how the label image will be arranged on the print medium. By looking at label OBJ16, the user can imagine what the label will look like with the label image printed on it. The input frame 16b is displayed along the outer edge of label OBJ16.

[0044] The user can create a label image OBJ16a (i.e., create a label image) by performing various editing operations on the label OBJ16 via the input unit 4. The various editing operations include direct operations within the input frame 16b, such as tapping, clicking, and other operations. The editing operations further include an operation of selectively specifying (for example, clicking) icons displayed on the toolbar 12, each of which is associated with a plurality of editing functions.

[0045] The label image creation application 5a has the above-mentioned multiple editing functions for creating a label image. In the first embodiment, the multiple editing functions include a text insertion function, a frame insertion function, a symbol insertion function, an image insertion function, a figure insertion function, a table insertion function, a barcode insertion function, a date and time insertion function, and a database reading function.

[0046] The text insertion function is a function that inserts text into the label image. The frame insertion function is a function that inserts a frame into the label image. The symbol insertion function is a function that inserts a symbol into the label image. The image insertion function is a function that inserts a separately prepared image into the label image. The shape insertion function is a function that inserts a shape into the label image. The table insertion function is a function that inserts a table (i.e., a table) into the label image. The barcode insertion function is a function that inserts a barcode into the label image. The date and time insertion function is a function that inserts text indicating the current date and time into the label image. The database reading function is a function that reads a separately prepared database and inserts the data contained in the read database into the label image.

[0047] The user can apply a desired editing function to the label image OBJ16a by selecting an icon associated with the desired editing function in the toolbar 12. Then, the user can edit the label image OBJ16a using the editing function. For example, by selecting an editing function OBJ corresponding to a function for inserting text, the user can insert text into the label image OBJ16a (and thus insert text into the label image). Then, the created label image can be printed by the printing device 101.

[0048] Here, the database read function will be described in more detail. The user can make the label image creation application 5a read the database by performing a predetermined read operation for reading the database. This read operation includes the operation of an icon in the toolbar 12 that corresponds to the database read function.

[0049] When a read operation is performed, the label image creation application 5a displays a database selection screen 20, as shown in Fig. 3, on the display unit 3. The database selection screen 20 may be displayed superimposed on the editing screen 10. The database selection screen 20 includes a browse button 21, an address bar 22, a table name box 23, and an OK button 25.

[0050] When the browse button 21 is operated, a database selection dialog (not shown) is displayed for selecting the database to be read. The database selection dialog lists the file names of selectable databases or images similar thereto. The user can select the database by selecting the file of the desired database from the database selection dialog.

[0051] A database has one or more data tables. A data table is also called a data sheet (or sheet). In the following description, a data table is simply referred to as a "table". A table includes multiple data fields in which data is stored or is stored. A data field may also be simply called a "field" or a "cell". Each data field includes text that indicates the data stored in that data field.

[0052] When a database to be read is selected, the file path of the selected database is displayed in the address bar 22. Furthermore, a table image 24 is displayed on the database selection screen 20. The table image 24 is an image showing one of the tables in the selected database.

[0053] Fig. 3 shows an example in which a database with the file name "test.xlsx" is selected as the database to be read. This database has, for example, three tables. The names of the three tables are, for example, "test_a", "test_b", and "test_c". Files with the extension "xlsx" are commonly used by Excel (a registered trademark of Microsoft Corporation), a well-known spreadsheet software.

[0054] The user can select a table to be previewed as a table image 24 by operating the table name box 23. Fig. 3 shows an example in which the table "test_a" has been selected and its table image 24 is displayed.

[0055] A table has one or more columns (or rows) and one or more records (or rows). Each data field belongs to one of the columns and one of the records. As shown in FIG. 3, the table "test_a" has a first column C1, a second column C2, and a third column C3. The table "test_a" also has a first record R1, a second record R2, and a third record R3. The table "test_a" further has a first row R0. The first row R0 specifies the names of each column. The first row R0 may also be used as a record.

[0056] When the OK button 25 is operated while any table is selected, the label image creation application 5a loads the currently selected database including the selected table. Then, the editing screen 10 is displayed, and table OBJ18 is displayed on the editing screen 10 as shown in FIG. 4. Table OBJ18 is an image showing the loaded database. More specifically, table OBJ18 in the first embodiment shows the selected table in the loaded database.

[0057] When the database is loaded, the editing area 13 of the editing screen 10 is divided into an image display area 14 and a database area 15. The table OBJ18 is displayed in the database area 15. At this time, a table box 17 is also displayed on the editing screen 10. The user can switch the table displayed as table OBJ18 to another table by operating the table box 17.

[0058] The user can add some or all of the data in the loaded database to the label image. That is, the user can add a data image representing each piece of data in the database to the label image. The addition of a data image to a label image will be specifically described below with reference to FIG. 5.

[0059] In the following description, data fields in a table may be expressed using corresponding columns and records. For example, a data field belonging to the first column C1 and the second record R2 may be referred to as the "C1-R2 field." In the example of FIG. 5, for example, the C1-R2 field stores data represented by the text "2019 / 04 / 30." Also, for example, the C3-R1 field stores data represented by the text "Aiu."

[0060] The label image creation application 5a accepts a merge operation by the user. The merge operation is a type of the above-mentioned editing operation. The merge operation is an operation that requests data in table OBJ18 to be inserted (i.e., added) to the label image. The merge operation in the first embodiment includes dragging and dropping a data field in table OBJ18, which contains data to be added to the label image, onto the label image OBJ16a.

[0061] For example, when a merge operation is performed to insert the C1-R1 fields into the label image OBJ16a, a data image OBJ161 showing a data image of the C1-R1 fields is added to the label image OBJ16a, as shown in Fig. 5. This generates a label image to which the data image has been added.

[0062] Furthermore, for example, when a merge operation is performed to insert the C3-R1 field into the label OBJ16, as shown in FIG. 5, a data image OBJ162 indicating a data image of the C3-R1 field is added to the label image OBJ16a.

[0063] In addition to merging on a data field basis, you can also merge on a column basis. For example, by merging a specific column name in the first row R0 to label OBJ16, you can add all the data contained in the corresponding column to the label image at once.

[0064] The label image creation application 5a can delete data merged into the label image OBJ16a from the label image OBJ16a in response to a predetermined merge cancel operation by the user. The label image creation application 5a can also delete a database loaded into the editing screen 10 in response to a predetermined database deletion operation by the user.

[0065] Note that the label image OBJ16a shown in FIG. 5 includes a graphic OBJ163. This graphic OBJ163 has been inserted using the graphic editing function described above. The label image OBJ16a shown in FIG. 5 is merely an example, and the label image may have any content. For example, the label image may include at least one image other than a graphic (e.g., text, a frame, a table, a barcode, an image, etc.). The label image does not have to include a data image. Conversely, the label image may include only a data image.

[0066] Here, various information and the like that is expanded in the memory 2b when the label image creation application 5a creates a label image will be described. Various processes by the label image creation application 5a, such as the creation of the label image described above and the storage of the label image described later, are performed using the memory 2b (and / or the storage unit 5).

[0067] That is, when the label image creation application 5a is started, it secures a work area, which is a working storage area, for example, in the memory 2b, and loads various programs, data, etc. into the work area to perform various processes.

[0068] When a label image is created on the editing screen 10, the label image creation application 5a writes LBX information in the work area. The LBX information is information about the label image being created, and indicates the contents of the label image. In other words, the LBX information includes information about what objects are placed in the label image, in what form, and where. When the label image is edited by the user, the LBX information is also updated.

[0069] Furthermore, when a database is loaded on the editing screen 10, the label image creation application 5a writes the loaded database in the work area. Furthermore, the label image creation application 5a adds a database path to the LBX information. The database path is the file path (i.e., the location) of the loaded database. For example, when a database with a file name "test" saved in a folder "C:\Work" is loaded, the database path "C:\Work\test" is added to the LBX information.

[0070] Furthermore, when a merge operation is performed on the editing screen 10, the label image creation application 5a adds data image information, which is information related to the merged data, to the LBX information. The data image information includes link information and format information. The link information indicates the location of the merged data. In other words, the link information indicates in which data field in the database the merged data is placed. If the database has multiple data tables, the link information further includes information indicating the table to which the merged data belongs. The format information indicates format information (e.g., size, font, etc.) of the data image showing the merged data.

[0071] Furthermore, when the above-mentioned merge cancellation operation is performed, the label image creation application 5a deletes the data image information corresponding to the data for which the merge cancellation operation is performed from the LBX information. Furthermore, when the above-mentioned database deletion operation is performed, the label image creation application 5a deletes the database path of the database to be deleted from the LBX information.

[0072] (1-5) Label image storage format The user can save the created label image by giving it a file name. The label image creation application 5a accepts a request to save the label image from the user. The save request may be made in any manner. In the first embodiment, the save request includes, for example, a predetermined input operation for displaying a file save dialog 40 illustrated in FIG. 8. This input operation includes, for example, an operation on the menu bar 11.

[0073] In the first embodiment, the created label image can be saved as a file in one of two file formats. In the first embodiment, the two file formats include the LBX format and the SLBX format.

[0074] FIG. 6 shows a schematic diagram of an LBX file 31, which is a file in the LBX format, and an SLBX file 30, which is a file in the SLBX format. (1-5-1) About the LBX format The LBX file 31 includes a layout information file 31a and a profile information file 31b. The LBX file 31 is generated by compressing the layout information file 31a and the profile information file 31b. The layout information file 31a and the profile information file 31b may each be in any file format. In the first embodiment, the layout information file 31a and the profile information file 31b are in XML format. Note that "XML" is an abbreviation for "Extensible Markup Language".

[0075] In the first embodiment, the above-mentioned LBX information is included in the layout information file 31a. That is, the layout information file 31a includes information on the created label image. If a database is displayed on the editing screen 10 (more specifically, table OBJ18 is displayed) when a save request is made, the LBX information contains the database path of that database. Therefore, the LBX file 31 (more specifically, layout information file 31a) generated in this case contains the database path.

[0076] In this case, if data is merged with the label image, that is, if a data image OBJ representing that data is included in the label image OBJ16a, the LBX information includes the data image information of that data, and therefore the LBX file 31 generated in this case includes that data image information.

[0077] The LBX file 31 further includes application information. The application information is information capable of identifying the label image creation application 5a for which a label image is about to be saved. The application information may include any information capable of identifying the label image creation application 5a. In the first embodiment, the application information includes an application name and version information. The application name is the name of the label image creation application 5a. The version information indicates the version of the label image creation application 5a.

[0078] The LBX file 31 further includes SLBX compatibility information, which is information indicating that the label image creation application 5a supports saving in the SLBX format, in other words, that saving in the SLBX format is possible.

[0079] The application information and the SLBX compatibility information may be included in any way and in any place in the LBX file 31. The application information and the SLBX compatibility information may be included in, for example, the profile information file 31b, the layout information file 31a, or may be included separately from these two files. Note that either the application information or the SLBX compatibility information may be omitted.

[0080] The LBX format is a file format in which the layout information file 31a and the profile information file 31b are integrated (compressed in the first embodiment) into one file. If the above-mentioned application information and SLBX compatibility information exist independently of these two files, these two files, the application information, and the SLBX compatibility information are integrated into one file.

[0081] The LBX file 31 does not include a database. In other words, in the SLBX format, as described below, a CSV file 32 indicating the database (more specifically, a table) displayed on the editing screen 10 is generated and saved together with the LBX file 31. However, in the LBX format, a database file is not generated, and the label image is saved independently of the database. The extension of the LBX file 31 in this first embodiment is "lbx".

[0082] (1-5-2) About the SLBX format The SLBX file 30 includes the above-mentioned LBX file 31. In addition to the LBX file 31, the SLBX file 30 further includes a CSV file 32 and a setting file 33.

[0083] The CSV file 32 stores a specific data table. The specific data table is one of one or more tables in a database that is loaded into the editing screen 10 and linked to the LBX information. More specifically, the specific data table is a table in which a merge operation has been performed on the editing screen 10, in other words, a table in which data incorporated into a label image currently being created is stored. In the first embodiment, for the sake of simplicity, a usage mode is assumed in which one table is selected by the user, and a label image in which data in the one table is incorporated is created and saved. In such a usage mode, the table selected by the user is the specific data table. Alternatively, the specific data table may be a table that was displayed on the editing screen 10 when a save request was received. Such a specific data table is saved as a CSV file 32, which is a file in CSV format. The CSV file 32 may include the entire database loaded into the editing screen 10, that is, all tables in the database.

[0084] In Figs. 3 to 5, as an example, a database in a file format commonly used in Excel, i.e., with an extension of "xlsx", is loaded. Then, table "test_a" is selected from among multiple data tables, and the data therein is incorporated into the label image. When the label image created in this way is saved in SLBX format, table "test_a" is saved as included in SLBX file 30. At this time, table "test_a" is converted to CSV format.

[0085] As is well known, the CSV format is a compatible (in other words, highly versatile) file format that can be used with multiple different application software. "CSV" is an abbreviation for "Comma Separated Value." The file extension for CSV format files is "csv."

[0086] The configuration file 33 contains various data used to save and / or open the SLBX file 30 . More specifically, the SLBX file 30 is an integration of the LBX file 31, the CSV file 32, and the setting file 33 into one file. Specifically, the SLBX file 30 is generated by compressing the LBX file 31, the CSV file 32, and the setting file 33 in a predetermined compression format. In the first embodiment, the predetermined compression format is the ZIP format. The SLBX format can be said to be a format in which a label image is integrated (specifically, compressed in the first embodiment) with a database into one file and then filed.

[0087] The standard extension for files compressed in ZIP format is "zip". Therefore, the extension of the SLBX file 30 may also be the standard extension "zip". However, in the first embodiment, a prescribed extension different from the standard extension of the ZIP format is used as the extension of the SLBX file 30. In the first embodiment, the prescribed extension is, for example, "slbx".

[0088] It should be noted that even if a database is not loaded on the editing screen 10, it is possible to save in the SLBX format. In this case, the SLBX file 30 does not include at least the CSV file 32. In other words, there may be an SLBX file 30 that does not have a CSV file 30. Also, when saving in the SLBX format, the LBX file 31 does not need to include the above-mentioned SLBX compatibility information.

[0089] (1-6) Opening and editing saved label files The label image creation application 5a can open a saved label file and display it on the editing screen 10. The label file is a general term for an SLBX file 30 saved in the SLBX format and an LBX file 31 saved in the LBX format.

[0090] For example, the user can specify a label file and make an open request. When an open request is made, the label image creation application 5a executes a file open process. The file open process is a process of opening the specified label file (hereinafter, referred to as the "file to be opened") and displaying it on the editing screen 10.

[0091] Specifically, the file open process includes displaying a label OBJ16 in the image display area 14 of the editing screen 10 based on the LBX file 31 included in the file to be opened. In the file open process, a label image OBJ16a based on the LBX information included in the file to be opened (specifically, the LBX file 31) is displayed in the label OBJ16.

[0092] If the file to be opened is an LBX file 31 saved in the LBX format and includes a database path, in the file open process, a table OBJ18 of the database existing at the location indicated by the database path is displayed in the database area 15 of the editing screen 10. If the LBX file 31 further includes data image information, a data image OBJ based on the data image information is added to the label image OBJ16a. If the database has multiple tables, any one of the tables may be displayed as the table OBJ18. For example, when saving, in addition to the database path, table information indicating the table that was displayed at the time of saving may be saved. If the file to be opened includes table information in addition to the database path, a table OBJ18 of the table indicated by the table information may be displayed.

[0093] Note that when saving in the LBX format, the database itself is not saved. Therefore, when an LBX file 31 saved in the LBX format is opened, even if a database path is included, it may happen that the database does not exist in that database path, or that the database path itself does not exist in the file system of the information processing device 1. In such a case, the database is not loaded on the editing screen 10, and the database area 15 and table OBJ18 are not displayed.

[0094] If the file to be opened is an SLBX file 30 and the SLBX file 30 includes a CSV file 32, then in the file open process, a table OBJ18 of the table indicated by the CSV file 32 is displayed in the database area 15 of the edit screen 10. If the SLBX file 30 further includes data image information, a data image OBJ based on the data image information is added to the label image OBJ16a. If the CSV file 32 includes information on multiple tables, any one of the tables may be displayed as the table OBJ18. For example, when saving, table information indicating the table that was displayed at the time of saving may be saved. If the SLBX file 30 includes table information, the table indicated by the table information may be displayed.

[0095] The label image creation application 5a opens the label file on the editing screen 10, and then edits the label image in response to an editing operation by the user, and further saves the edited label image in response to a save request.

[0096] The information processing device 1 may include a media interface (e.g., a USB interface) (not shown). The label image creation application 5a can read a label file via the media interface, display it on the editing screen 10, and accept editing operations.

[0097] (1-7) Save label image When the user makes a save request while the editing screen 10 is displayed, the label image creation application 5a displays a file save dialog 40 as exemplified in Fig. 8. However, the label image creation application 5a does not unconditionally display the file save dialog 40. Before displaying the file save dialog 40, the label image creation application 5a determines whether or not to display the message window 36 in Fig. 7.

[0098] In the first embodiment, basically, when a database is displayed on the editing screen 10 (i.e., table OBJ18 is displayed) when a save request is made (hereinafter referred to as a "database read state"), it is determined that the message window 36 should be displayed. If the database is not read when a save request is made, it is determined that displaying the message window 36 is unnecessary.

[0099] However, in this first embodiment, even if the database is in a loaded state when a save request is made, if the label image currently being created is not a new one but rather an SLBX file 30 that was originally opened, edited as necessary, and is about to be saved again, it is determined that there is no need to display the message window 36.

[0100] Furthermore, in this first embodiment, if the label image currently being created is (i) not a new one but an LBX file with a path that was originally opened, edited as necessary, and then saved again, and (ii) the previous save execution application supports saving in SLBX format, it is determined that there is no need to display the message window 36.

[0101] An LBX file with path means an LBX file 31 that is saved in the LBX format and contains a database path. The save execution application means software that previously saved the currently open label file. The save execution application may be the label image creation application 5a itself, or may be software different from the label image creation application 5a.

[0102] When the label image creation application 5a determines that the message window 36 should be displayed, the label image creation application 5a displays the message window 36, as shown in FIG. The message window 36 includes a message 36a. The message 36a indicates that the created label image can be saved in the SLBX format. In other words, displaying the message 36a notifies the user that saving in the SLBX format is possible. By seeing this message 36a, the user can recognize that the label image can be saved in the SLBX format.

[0103] The message window 36 includes an OK button 37. When the user operates the OK button 37, the label image creation application 5a erases the message window 36 and displays a file save dialog 40, as shown in Fig. 8, on the display unit 3. When a save request is made and it is determined that it is not necessary to display the message window 36, the label image creation application 5a displays the file save dialog 40 without displaying the message window 36.

[0104] As shown in FIG. 8, the file save dialog 40 includes a navigation pane 41, a file name box 42, a file type box 43, and a Save button 44. A folder tree managed by the OS is displayed in the navigation pane 41. Each folder in the folder tree is actually assigned to, for example, the storage unit 5. The user can specify a folder in which to save a label image by operating the navigation pane 41. The label image creation application 5a saves the label image in the specified folder.

[0105] The user can input a file name of the label image in the file name box 42. The label image creation application 5a determines the input file name as the file name of the file to be saved.

[0106] The user can further specify the format in which the label image is to be saved in a file type box 43. In the file type box 43, one of a plurality of selectable types of saving formats is displayed.

[0107] The initial value of the save format is determined in advance for each condition before saving. The initial value of the save format means the save format that is first displayed in the file type box 43 when the file save dialog 40 is displayed, in other words, the save format that is set as the default.

[0108] In the first embodiment, when an SLBX file 30 is opened, the SLBX format is set as the default, and when an LBX file 31 saved in the LBX format is opened, the LBX format is set as the default.

[0109] When the file type box 43 is operated, a pull-down menu 45 is displayed in which selectable saving formats are listed, as shown in Fig. 9. In the pull-down menu 45, "Extended layout file" indicates the SLBX format, and "Standard layout file" indicates the LBX format. The user can specify the saving format by selecting the desired saving format from the pull-down menu 45. The label image creation application 5a saves the label image in the specified saving format.

[0110] FIG. 9 shows, as an example, a state in which “C:￥work” is specified as the destination folder, “myAbc” is specified as the file name for saving, and the save format is about to be changed to “SLBX format.”

[0111] (1-8) Main processing The save process executed by the control unit 2 to realize various processes including the creation and saving of the label image described above will be described with reference to Fig. 10. The main process is included in the label image creation application 5a. That is, the main process is executed by the control unit 2 executing a corresponding program module in the label image creation application 5a. When the control unit 2 (more specifically, the CPU 2a) is started, it periodically and repeatedly executes the main process.

[0112] When the control unit 2 starts the main process, it determines in S10 whether or not an open request has been made by the user. If an open request has been made, the control unit 2 displays the edit screen 10 on the display unit 3 in S20.

[0113] In S30, the control unit 2 executes the file open process described above. That is, the control unit 2 reads the file to be opened. Then, the control unit 2 displays a label image OBJ16a based on a layout information file 31a included in the file to be opened on the editing screen 10. If the file to be opened includes a database path, the control unit 2 displays a table OBJ18 based on the database path on the editing screen 10. After the process of S30, the control unit 2 executes a label creation process in S60.

[0114] If an open request has not been made in S10, the control unit 2 proceeds to S40. In S40, the control unit 2 determines whether a new creation trigger has occurred. If a new creation trigger has not occurred, the control unit 2 ends this main process.

[0115] When a new creation trigger occurs, the control unit 2 displays the editing screen 10 on the display unit 3 in S50. More specifically, the control unit 2 displays the initial state of the editing screen 10 (see FIG. 2). After the process of S50, the control unit 2 executes a label creation process in S60.

[0116] In S60, the control unit 2 creates a label image in response to the various editing operations by the user described above. Specifically, the control unit 2 adds text, figures, tables, barcodes, and other images to the label image, changes the form (e.g., size, shape, color, font, etc.) of the added image, moves the added image, and deletes the added image. In addition, the control unit 2 loads a database into the editing screen 10 and merges data in the loaded database into the label image in response to user operations.

[0117] Then, in S70, the control unit 2 determines whether or not a save request has been made by the user. If a save request has not been made, the process proceeds to S60. In other words, in this case, the label creation process continues. If a save request has been made, the process proceeds to S80. In S80, the control unit 2 executes the save process. Details of the save process are as shown in FIG. 11.

[0118] 11, the control unit 2 judges in S110 whether or not the SLBX file 30 is open. Specifically, the SLBX file 30 is open when the label image currently being created is originally displayed when the SLBX file 30 is opened, and a save request has been made while the file is open, or when the file has been opened, edited, or the like, and a save request has been made.

[0119] If the SLBX file 30 is open, the process proceeds to S180. In S180, the control unit 2 displays the file save dialog 40 on the display unit 3. At this time, the SLBX format is displayed as the default (initial value) in the file type box 43. After the process of S180, the process proceeds to S190. Note that even if the SLBX file 30 is open, if the database was deleted from the editing screen 10 when saving, the LBX format may be displayed as the default in S180.

[0120] If the SLBX file 30 is not open in S110, the process proceeds to S120. Examples of cases in which the process proceeds to S120 include when a new label image is created and when an LBX file 31 saved in the LBX format is opened.

[0121] In S120, the control unit 2 determines whether or not a database (specifically, table OBJ18 is displayed) is displayed on the editing screen 10. If a database is displayed, the process proceeds to S130.

[0122] In S130, the control unit 2 judges whether the LBX file with a path is open or not. In other words, it judges whether the label image to be saved is not a newly created one, but rather an LBX file with a path that was originally opened and edited as necessary.

[0123] When an LBX file with a path is opened and the editing screen 10 is displayed, a label image and a database based on the LBX file with a path are displayed on the editing screen 10, editing, etc. is performed as necessary, and the file is then saved again, then in S130 it is determined that an LBX file with a path has been opened.

[0124] If an LBX file with a path is not open in S130, the process proceeds to S160. In other words, if a new label image is created and a database is loaded when it is saved, the process proceeds from S130 to S160. Alternatively, if an LBX file 31 that does not include a database path is opened and then a database is loaded and saved, the process also proceeds from S130 to S160.

[0125] In S160, the control unit 2 performs a notification process. Specifically, a message window 36 illustrated in Fig. 7 is displayed on the display unit 3. Then, when the OK button 37 of the message window 36 is operated, the process proceeds to S170.

[0126] In S170, the control unit 2 displays the file save dialog 40 on the display unit 3. At this time, the LBX format is displayed as the default (initial value) in the file type box 43. After the process of S170, the process proceeds to S190.

[0127] If the database is not displayed on the edit screen 10 in S120, the process proceeds to S170. That is, the notification process in S160 is not executed, and the file save dialog 40 is displayed in S170. In other words, the execution of the notification process (and thus the display of the message 36a) is avoided.

[0128] If the LBX file with the path is opened in S130, the control unit 2 executes the previous application check process in S140. The previous application check process is a process for checking whether the previously saved application supports saving in the SLBX format. The details of the previous application check process are as shown in FIG.

[0129] When the control unit 2 proceeds to the previous application confirmation process, it determines in S310 whether the open target file contains SLBX compatible information. If SLBX compatible information is included, the control unit 2 determines in S320 that the previous save execution application supports saving in the SLBX format. After the process of S320, the process proceeds to S150 (FIG. 11).

[0130] If the file to be opened does not contain SLBX compatibility information in S310, the process proceeds to S330. In S330, the control unit 2 determines whether the file to be opened contains application information. If the file to be opened does not contain application information, the process proceeds to S370. If the file to be opened contains application information, the process proceeds to S340.

[0131] In S340, the control unit 2 acquires application information included in the file to be opened. The application information includes the application name and version information of the previously saved and executed application. In S350, the control unit 2 checks whether the previously saved application supports saving in the SLBX format by performing a predetermined communication based on the application information with the server 200. In this case, a specific checking method may be appropriately determined.

[0132] As described above, the server 200 has SLBX compatibility information. The SLBX compatibility information includes information on whether or not saving in the SLBX format is supported for each of one or more pieces of software capable of creating label images (hereinafter referred to as "label applications"). More specifically, the SLBX compatibility information has information on whether or not saving in the SLBX format is supported for each label application and for each version of each of those label applications. The label applications may include the label image creation application 5a.

[0133] The control unit 2 may, for example, transmit the application information acquired in S340 to the server 200. When the server 200 receives the application information, the server 200 may refer to the SLBX compatibility information to determine whether or not the label application corresponding to the received application information supports saving in the SLBX format. The server 200 may transmit the determination result to the information processing device 1. The label image creation application 5a may check whether or not the previous save execution application supports saving in the SLBX format based on the determination result transmitted from the server 200.

[0134] Also, for example, the control unit 2 may acquire SLBX compatibility information from the server 200. Then, the control unit 2 may check whether the previously saved application supports saving in the SLBX format by comparing the acquired SLBX compatibility information with the application information acquired in S340.

[0135] In S360, the control unit 2 judges whether or not it has been confirmed that the previous save execution application supports saving in the SLBX format. If it has been confirmed that it supports saving in the SLBX format, the process proceeds to S320. That is, it is judged that the previous save execution application supports saving in the SLBX format. On the other hand, if it has been confirmed that it does not support saving in the SLBX format, the process proceeds to S370.

[0136] In S370, the control unit 2 determines that the previously executed save application does not support saving in the SLBX format. After the process of S370, the process proceeds to S150 (FIG. 11). In S150, it is determined whether or not the previously executed saved application supports saving in the SLBX format, based on the result of the previous application check process in S140.

[0137] If the previously executed save execution application does not support saving in the SLBX format, a notification process is executed in S160, and the process proceeds to S170. On the other hand, if the previous save execution application supports saving in the SLBX format, the process proceeds to S170 without proceeding to S160. In other words, in this case, the notification process of S160 is avoided and the file save dialog 40 is displayed.

[0138] In S190, the control unit 2 accepts various inputs to the file save dialog 40. As described above, the various inputs include designation of a destination folder, designation of a file name for saving, designation of a save format, and operation of the save button 44. When the save button 44 is operated, the process proceeds to S200.

[0139] In S200, the control unit 2 determines the designated save format. If the LBX format is designated, the process proceeds to S220. In S220, the control unit 2 executes the LBX save process. Specifically, the control unit 2 generates an LBX file 31 based on the state of the editing screen 10 when the save request is made. Then, the control unit 2 saves the generated LBX file 31 in a designated folder with a designated file name.

[0140] If the SLBX format is specified in S200, the process proceeds to S210. In S210, the control unit 2 executes an SLBX save process. Specifically, the control unit 2 generates an LBX file 31 based on the state of the editing screen 10 when the save request is made. If a database is displayed on the editing screen 10, the control unit 2 generates a CSV file 32 based on that database. The control unit 2 further generates a setting file 33. Then, as described above, a single SLBX file 30 is generated that includes the generated LBX file 31, CSV file 32, and setting file 33. The generated SLBX file 30 is then saved in a specified folder with a specified file name.

[0141] (1-9) Effects of the First Embodiment According to the first embodiment described above, the following advantages (1a) to (1h) are obtained. (1a) A user who uses the label image creation application 5a may not know that label images can be saved in the SLBX format. Specifically, for example, the user may know that the SLBX format exists, but may not know that the label image creation application 5a that he or she is currently using supports the SLBX format (or may believe that it does not support it). Or, the user may not even know what the SLBX format is.

[0142] In contrast, the label image creation application 5a of the first embodiment basically performs a notification process (S160) if a database is displayed on the editing screen 10 when a save request is made.

[0143] This allows the user to recognize that saving in the SLBX format is possible. The user can then select saving in the SLBX format as necessary. Saving in the SLBX format allows label images and the database to be managed efficiently and collectively.

[0144] The label image creation application 5a may be updated in response to an update operation by the user himself or automatically. Specifically, the label image creation application 5a may be capable of receiving an update request operation from the user. In response to the update request operation, the label image creation application 5a may check with an external device (e.g., the server 200) whether or not a newer version of the label image creation application 5a (hereinafter referred to as a "new version application") than the current version exists. Alternatively, the label image creation application 5a may check with an external device at a predetermined update check timing whether or not a new version application exists. Then, if a new version application exists, the label image creation application 5a may obtain the new version application and update the currently installed label image creation application 5a to the new version application.

[0145] The present disclosure is effective even when the label image creation application 5a has an update function. That is, for example, it may happen that the application did not support saving in the SLBX format before the update, but the application supports the SLBX format after the update. In such a case, the user can easily know at an appropriate time that the upgrade has made it possible to save in the SLBX format.

[0146] (1b) In the first embodiment, the notification process is performed by displaying a message 36a (FIG. 7). Therefore, the user can easily know that saving in the SLBX format is possible.

[0147] (1c) The message 36a is displayed before the file save dialog 40 is displayed. Therefore, the user can know that saving in the SLBX format is possible before selecting a save format in the file save dialog 40. Therefore, the user can efficiently select a save format in the file save dialog 40.

[0148] (1d) When the SLBX file 30 is opened and saved again, no notification process is performed (S110→S180). In addition, in this case, the SLBX format is displayed by default in the file save dialog 40 (S180).

[0149] One of the reasons for this configuration is that a user who opens an SLBX file 30 may already know the SLBX format, and may find the notification process annoying for such a user. In addition, it is expected that a user who opens an SLBX file 30 will likely want to save the file in the SLBX format when saving it again. Therefore, when the file to be opened is an SLBX file 30, the notification process is not performed and the SLBX format is displayed by default in the file save dialog 40, thereby improving usability for such users.

[0150] (1e) When a path-attached LBX file is opened and saved again with the database displayed on the editing screen 10 (S130: YES), a previous application check process is executed (S140). That is, it is confirmed whether the save execution application that previously saved the path-attached LBX file supports saving in the SLBX format. If the save execution application supports the SLBX format (S150: YES), the notification process is avoided and the file save dialog 40 is displayed.

[0151] One of the reasons for this configuration is that if the previous save execution application supports the SLBX format but the file was saved in the LBX format, the user may have intentionally selected to save in the LBX format, knowing that saving in the SLBX format is possible. In other words, the user may prefer to manage files in the LBX format even if the label image contains data. For such users, it may be more convenient to not have the notification process performed.

[0152] On the other hand, if the save execution application does not support the SLBX format (S150: NO), a notification process is executed. One of the reasons for this configuration is that in this case, the user may not know that the label image creation application 5a supports saving in the SLBX format or may not know the SLBX format itself. For such users, the convenience is improved by the notification process.

[0153] (1f) When a newly created label image is saved, or when an LBX file 31 saved in LBX format is opened and saved again, there is a possibility that the user will want to save in LBX format even if notification processing has been performed. Therefore, in this first embodiment, in such cases, the LBX format is displayed by default in the file save dialog 40. This allows for convenience for users who want to save in LBX format, while still performing notification processing as necessary.

[0154] (1g) In the first embodiment, when a label image is saved in the LBX format, SLBX compatibility information is included in the LBX file 31. As a result, when the LBX file 31 is opened later and saved again, it is easily confirmed in the previous application confirmation process of S140 that the previously saved and executed application is compatible with the SLBX format (S310→S320).

[0155] (1h) In the first embodiment, when a label image is saved, application information is included in the label file. This application information may be referred to in the previous application confirmation process of S140. That is, in the first embodiment, it is also possible to determine whether the previously saved and executed application is compatible with the SLBX format based on the application information. In the first embodiment, the determination is made by communicating with the server 200 and based on the SLBX compatibility information and application information held by the server 200. Therefore, a highly reliable determination result can be obtained. In addition, by having the SLBX compatibility information held by the server 200, the capacity of the storage unit 5 in the information processing device 1 can be made more generous than when the information processing device 1 itself holds the SLBX compatibility information.

[0156] (1-10) Correspondence of terms The label image creation application 5a corresponds to an example of an image creation program in the present disclosure. The image display area 14 corresponds to an example of a first area in the present disclosure, and the database area 15 corresponds to an example of a second area in the present disclosure. The label image corresponds to an example of a print image in the present disclosure. The SLBX format corresponds to an example of a first storage format in the present disclosure, and the LBX format corresponds to an example of a second storage format in the present disclosure. In the SLBX file 30, the LBX file 31 corresponds to an example of an image information file in the present disclosure, and the CSV file 32 corresponds to an example of a database file in the present disclosure. The file save dialogue 40 corresponds to an example of a save format selection screen in the present disclosure. In the file type box 43 of the file save dialogue 40, the display of "extended layout file" indicating the SLBX format corresponds to an example of the first information in the present disclosure, and the display of "standard layout file" indicating the LBX format corresponds to an example of the second information in the present disclosure. The database path corresponds to an example of database location information in the present disclosure. The SLBX compatibility information corresponds to an example of the compatibility information in the present disclosure. The SLBX compatibility information corresponds to an example of the availability information in the present disclosure. The application information corresponds to an example of attribute information in the present disclosure. The server 200 corresponds to an example of an information holding device in the present disclosure.

[0157] S20, S30, S50, and S60 correspond to an example of an editing screen display process in the present disclosure. S30 and S60 correspond to an example of a database display process and a print image creation process in the present disclosure. S140 corresponds to an example of a determination process in the present disclosure. S190 corresponds to an example of a storage format acceptance process in the present disclosure. S350 corresponds to an example of an acquisition process in the present disclosure.

[0158] [2. Second embodiment] The second embodiment has a basic configuration similar to that of the first embodiment, so the differences will be described below.

[0159] The printing system of the second embodiment differs from the printing system of the first embodiment mainly in the contents of the save process. That is, in the first embodiment, the process of FIG. 11 was executed as the save process of S80 of the main process. In contrast, in the second embodiment, the save process illustrated in FIG. 13 is executed. Note that in the save process of FIG. 13, the same processes as those in the save process of FIG. 11 are given the same reference numerals as in FIG. 11, and their description will be omitted. Below, the save process of FIG. 13 will be described focusing on the differences from FIG. 11.

[0160] If a database is displayed on the editing screen 10 in S120, the process proceeds to S125. In S125, the control unit 2 determines whether data is merged into the label image OBJ16a. If data is not merged, the process proceeds to S170. If data is merged, the process proceeds to S130.

[0161] The processes of S130 to S150 are basically the same as those of the first embodiment. However, if it is determined in S130 that the LBX file with the path is not open, and if it is determined in S150 that the previous save execution application does not support saving in the SLBX format, in this second embodiment, the message window 36 is not displayed and the process proceeds to S165.

[0162] In S165, the control unit 2 displays a file save dialog 46, as exemplified in FIG. 14, on the display unit 3, and executes a notification process. In the file save dialog 46 in FIG. 14, the SLBX format is displayed as the initial value of the file type box 43. This corresponds to the notification process. In other words, by displaying the SLBX format as the default, the user is notified that saving in the SLBX format is possible. The file save dialog 46 further displays a message 36a. This message 36a allows the user to know more reliably that saving in the SLBX format is possible, and also allows the user to learn the outline of the SLBX format.

[0163] 3. Other embodiments Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modified forms.

[0164] (3-1) The specific contents of the message 36a, and in turn the specific contents of the notification process, may be any contents that can make the user aware that saving in the SLBX format is possible.

[0165] The message 36a may be displayed whenever, wherever and in any manner in the display area of ​​the display unit 3. The display in the form of a pop-up window as exemplified in Fig. 7 is merely one example.

[0166] (3-2) In the previous application confirmation process of FIG. 12, the process of S310 may be omitted. Conversely, the processes of S330 to S360 may be omitted. In other words, if the LBX file 31 does not contain the SLBX compatible information (S310: NO), the process may proceed to S370.

[0167] (3-3) In S220 of Fig. 11, only one of the SLBX compatibility information and the application information may be included in the LBX file 31. If the LBX file 31 includes SLBX compatibility information but not application information, S330 to S360 may be omitted in Fig. 12. Conversely, if the LBX file 31 includes application information but not SLBX compatibility information, S310 may be omitted in Fig. 12.

[0168] (3-4) The SLBX compatibility information may include any information that can identify whether or not the SLBX format is supported based on the application information. In each of the above embodiments, the server 200 has the SLBX compatibility information. However, the SLBX compatibility information may exist anywhere. An information processing device other than the information processing device 1 and the server 200 may have the SLBX compatibility information, and the SLBX compatibility information may be acquired from the other information processing device.

[0169] The information processing device 1 may have the SLBX compatibility information. In other words, the label image creation application 5a or other application software (hereinafter referred to as "internal application") in the information processing device 1 may have the SLBX compatibility information. The internal application may have the SLBX compatibility information from the beginning. That is, the installer of the internal application may include the SLBX compatibility information, and the internal application may be configured to store the SLBX compatibility information when the internal application is installed in the information processing device 1. Alternatively, the internal application may obtain the SLBX compatibility information from an external device (e.g., the server 200) after the internal application is installed in the information processing device 1. The internal application may appropriately update the SLBX compatibility information that it possesses. Specifically, the internal application may periodically communicate with the external device to check whether the SLBX compatibility information has been updated, and if it has been updated, obtain the information and update its own SLBX compatibility information.

[0170] (3-5) In the storage process of FIG. 13, the process of S125 may be omitted. In the saving process of FIG. 11, the process of S125 may be added between S120 and S130, as in the case of FIG.

[0171] (3-6) The notification process of the first embodiment may include, instead of (or in addition to) displaying the message window 36, displaying the message 36a or a similar message in the file save dialog 40 as in FIG. 14.

[0172] In the second embodiment, the file save dialog 46 in FIG. 14 may not include the message 36a. (3-7) The present disclosure may also be applied when a label file in SLBX format is opened and saved again. In other words, even if a file in SLBX format is opened, if a database is displayed on the editing screen 10 when the file is saved again, a notification process may be performed. Specifically, the processes of S110 and S180 may be omitted from the save process in FIG. 11 and / or FIG. 13.

[0173] (3-8) Either one of the first and second communication units 6 and 7 may be omitted. In other words, the same communication unit may be capable of communicating with both the printing device 101 and the server 200. (3-9) Multiple functions possessed by one component in the above embodiments may be realized by multiple components, or one function possessed by one component may be realized by multiple components. Also, multiple functions possessed by multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Also, part of the configuration of the above embodiments may be omitted. Also, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments. [Explanation of symbols]

[0174] 1...information processing device, 2...control unit, 2a...CPU, 2b...memory, 3...display unit, 4...input unit, 5...memory unit, 5a...label image creation application, 6...first communication unit, 7...second communication unit, 10...editing screen, 14...image display area, 15...database area, 16a...label image object, 30...SLBX file, 31...CSV file, 36...message window, 36a...message, 40, 46...file save dialog, 43...file type box, 44...save button, 45...pull-down menu, 101...printing device, 200...server.

Claims

1. a first communication unit configured to communicate with the printing device; A display unit; An input unit; A control unit; An image creation program executable by the control unit in an information processing device comprising: The control unit, an editing screen display process for displaying an editing screen having a first area and a second area on the display unit; a database display process for displaying a database in the second area in response to a database display request for requesting display of the database; a print image creation process for creating a print image, which is an image to be printed by the printing device, in accordance with an editing operation by a user via the input unit and displaying the print image in the first area, the editing operation including adding data included in the database displayed in the second area to the print image; a storage format receiving process for receiving a designation of a first storage format or a second storage format in response to a storage request for requesting storage of the print image, the first storage format is a format in which the print image created in the print image creation process and the database in a case where the database is displayed on the editing screen when the save request is received are integrated into one file and saved; the second storage format is a format in which an image information file indicating the print image created in the print image creation process is stored independently from the database; A storage format acceptance process; (i) receiving the save request, and (ii) notifying the user that saving in the first save format is possible when the database is displayed on the editing screen at the time the save request is received; An image creation program that executes the following:

2. 2. The image creation program according to claim 1, The notification process includes displaying a message on the display unit indicating that the data can be saved in the first saving format. Image creation program.

3. 3. The image creation program according to claim 2, The storage format reception process includes: displaying a storage format selection screen on the display unit for accepting designation of the storage format; displaying, in response to a selection operation by the user via the input unit, either first information indicating the first storage format or second information indicating the second storage format on the storage format selection screen in a selective manner; accepting a designation of the storage format corresponding to the first information or the second information displayed on the storage format selection screen; Including, The notification process is executed before the storage format selection screen is displayed, or while the storage format selection screen is displayed. Image creation program.

4. 2. The image creation program according to claim 1, The storage format reception process includes: displaying a storage format selection screen on the display unit for accepting designation of the storage format; displaying, in response to a selection operation by the user via the input unit, either first information indicating the first storage format or second information indicating the second storage format on the storage format selection screen in a selective manner; accepting a designation of the storage format corresponding to the first information or the second information displayed on the storage format selection screen; Including, The notification process includes displaying the first information as an initial value on the storage format selection screen. Image creation program.

5. The image creation program according to any one of claims 1 to 4, the second storage format includes adding database location information indicating a location of the database to the image information file when the database is displayed on the editing screen at the time the storage request is received, The image creation program further includes the control unit: a file open process for opening the image information file stored in the second storage format and including the database location information; a determination process for determining whether or not a save execution application, which is a computer program that has saved the image information file before it is opened by the file open process, is capable of saving the image information file in the first save format; Run the command, The save / execute application includes the image creation program, the print image creation process includes displaying, in the first area, the print image indicated by the image information file opened by the file open process; the database display process includes, when the image information file opened by the file open process includes the database location information, displaying, in the second area, the database that exists at the location indicated by the database location information; the image creation program is configured to, when receiving the save request after the file open process is executed, execute or avoid the notification process depending on a result of the determination process. Image creation program.

6. 6. The image creation program according to claim 5, (i) the save request is received after the file open process is executed, (ii) the database is displayed on the edit screen when the save request is received, and (iii) it is determined by the determination process that the save execution application cannot execute the save in the first save format, the notification process is executed. Image creation program.

7. 6. The image creation program according to claim 5, (i) the save request is received after the file open process is executed, (ii) the database is displayed on the editing screen when the save request is received, and (iii) if it is determined by the determination process that the save execution application is capable of saving in the first save format, execution of the notification process is avoided. Image creation program.

8. 6. The image creation program according to claim 5, The storage format reception process includes: displaying a storage format selection screen on the display unit for accepting designation of the storage format; displaying, in response to a selection operation by the user via the input unit, either first information indicating the first storage format or second information indicating the second storage format on the storage format selection screen in a selective manner; accepting a designation of the storage format corresponding to the first information or the second information displayed on the storage format selection screen; Including, The image creation program is configured to: (i) receive the save request after the file open process is executed; (ii) the database is displayed on the editing screen when the save request is received; and (iii) if the determination process determines that the save execution application is capable of saving in the first save format, to avoid execution of the notification process and to display the second information on the save format selection screen that is displayed immediately after the start of the save format reception process. Image creation program.

9. 6. The image creation program according to claim 5, the save execution application capable of saving in the first save format is configured to add, when saving the print image in the second save format, to the image information file, correspondence information indicating that the save execution application also supports saving in the first save format; The determination process determines that the save execution application is capable of saving in the first save format when the image information file opened by the file open process contains the correspondence information, and determines that the save execution application is not capable of saving in the first save format when the correspondence information is not contained. Image creation program.

10. 6. The image creation program according to claim 5, the storage execution application is configured to add attribute information capable of identifying the storage execution application to the image information file to be stored, regardless of the storage format; the image creation program is configured to have or be able to acquire availability information indicating whether the save execution application corresponding to the attribute information is capable of saving the image in the first save format; The determination process acquires the attribute information included in the image information file opened by the file open process, and determines whether the save execution application is capable of saving the image in the first save format by referring to the capability information based on the acquired attribute information. Image creation program.

11. 11. The image creation program according to claim 10, the information processing device includes a second communication unit configured to communicate with an information holding device in which the availability information is stored; The image creation program further includes the control unit: an acquisition process of acquiring the availability information from the information holding device via the second communication unit when the image information file is opened by the file open process; Run The determination process determines whether or not the save execution application is capable of saving the data in the first save format, based on the capability information acquired by the acquisition process. Image creation program.

12. 2. The image creation program according to claim 1, and if the data has not been added to the print image being created when the save request is received, execution of the notification process is avoided. Image creation program.

13. 2. The image creation program according to claim 1, the first storage format is a format in which the image information file and the database file indicating the database are collectively compressed in a predetermined compression format to generate the single file; Image creation program.

14. 2. The image creation program according to claim 1, the print image is printed on the long-sized print medium along a length direction while the print medium is transported in the length direction in the printing device; Image creation program.

15. a communication unit configured to communicate with the printing device; A display unit; An input unit; A control unit; Equipped with The control unit is an editing screen display process for displaying an editing screen having a first area and a second area on the display unit; a database display process for displaying a database in the second area in response to a database display request for requesting display of the database; a print image creation process for creating a print image, which is an image to be printed by the printing device, in accordance with an editing operation by a user via the input unit and displaying the print image in the first area, the editing operation including adding data included in the database displayed in the second area to the print image; a storage format receiving process for receiving a designation of a first storage format or a second storage format in response to a storage request for requesting storage of the print image, the first storage format is a format in which the print image created in the print image creation process and the database in a case where the database is displayed on the editing screen when the save request is received are integrated into one file and saved; the second storage format is a format in which an image information file indicating the print image created in the print image creation process is stored independently from the database; A storage format acceptance process; (i) receiving the save request, and (ii) notifying the user that saving in the first save format is possible when the database is displayed on the editing screen at the time the save request is received; An information processing device configured to execute the above.

Images