Image processing program and information processing apparatus

Abstract

To provide a technique capable of easily processing a print image associated with data of a database.SOLUTION: An information processing apparatus can store a first-type extended image file formed by compressing a first image file and a database file. The first image file indicates a first print image to be able to be printed by a printer. The first print image includes an object associated with specific data in a database. A control unit displays, when the first-type extended image file is selected, first file information indicating the first image file and database information indicating the database file, in association with each other. On receipt of an instruction to transfer the first-type extended image file, the control unit transfers the first image file and the database file to the printer.SELECTED DRAWING: Figure 8

Description

[Technical Field]

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

[0002] Patent Document 1 discloses a label production system configured to transfer print data created on a PC to a label production device. With this label production system, after the print data is transferred, the label production device can read the print data by itself and create a print label on which the print data is printed.

[0003] Furthermore, a technology has already been put into practical use in which a label image containing an object associated with database data is generated by an information processing device, and a label layout file showing the label image and a database file are transferred to a printer. With this technology, the user selects the label layout file and the database file on a transfer screen displayed on the information processing device, and the selected files are transferred to the printer. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-119197 [Patent Document 2] Japanese Patent Application Publication No. 2019-211904 Summary of the Invention [Problem to be solved by the invention]

[0005] To make it easier for users to manage, one idea is to save the label layout file and the associated database file in an expanded file format, in which they are compressed into a single file. When transferring a label image saved in this expanded file format to a printer, the compressed label layout file and database file can be decompressed, and both files can be displayed on a transfer screen, where they can be selected and transferred to the printer.

[0006] However, if the transfer screen simply displays the label layout file and database file, it is difficult to tell whether the two are related, which reduces the efficiency of selecting the file to be transferred. This problem can become even more pronounced when other label layout files or other database files are mixed in on the transfer screen.

[0007] It is desirable that one aspect of the present disclosure be able to easily select an image file and a database file associated therewith in an information processing device and transfer them to a printing device. [Means for solving the problem]

[0008] According to one aspect of the present disclosure, there is provided an image processing program executable by an information processing apparatus including a storage unit, a display unit, a communication unit, and a control unit, the communication unit being capable of communicating with a printing device.

[0009] The storage unit is capable of storing a first type extended image file. The first type extended image file is a file in which a first image file and a database file are compressed in a predetermined compression format. The database file represents a database. The first image file represents a first print image that can be printed by a printing device. The first print image includes an object associated with specific data in the database, and the object represents the data.

[0010] The control unit is capable of executing an image processing program, which causes the control unit to execute a display process and a transfer process. In response to a first type extended image file being selected as a candidate for transfer to a printing device, the display process links first file information indicating the first image file and database information indicating the database file together and displays them on a display unit.

[0011] In the transfer process, after the display process is executed, in response to receiving an instruction to transfer the first type extended image file, the first image file and the database file are transferred to the printing device via the communication unit. By executing such an image processing program, when a first type extended image file is selected as a transfer candidate in the information processing device, first file information and database information indicating the first image file and database file included in the first type extended image file, respectively, are displayed in association with each other, allowing the user to easily select the first image file and the associated database file and transfer them to the printing device. Displaying the first file information and the database information in association with each other may be interpreted as, for example, displaying the first file information and the database information in a manner that allows a user who views the first file information and the database information to recognize that they (and thus the first image file and the database file) are related or may be related to each other. Specific display manners, which are merely examples, may include displaying these two pieces of information so that they are contained within a specific partitioned section or area, or displaying these two pieces of information with a predetermined object attached to them that indicates that they are related to each other. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a configuration diagram of a printing system according to an embodiment. [Figure 2] FIG. 2 is an explanatory diagram of a home screen. [Figure 3] FIG. 10 is an explanatory diagram showing an example of a label image and a database associated with the label image; [Figure 4] FIG. 2 is an explanatory diagram of the structure of a label file. [Figure 5] FIG. 10 is an explanatory diagram of a transfer screen in an initial state. [Figure 6] FIG. 10 is an explanatory diagram of a transfer candidate selection screen. [Figure 7] FIG. 10 is an explanatory diagram of a transfer screen in which transfer candidate files are displayed in an unexpanded state. [Figure 8] FIG. 10 is an explanatory diagram of a transfer screen in which transfer candidate files are displayed in an expanded state. [Figure 9] 10 is a flowchart of a transfer control process. [Figure 10] 10 is a part of a flowchart of a transfer process. [Figure 11] 10 is a remaining part of the flowchart of the transfer process. DETAILED DESCRIPTION OF THE INVENTION

[0013] Exemplary embodiments of the present disclosure will now be described. [1. Embodiment] (1-1) Printing system configuration 1, the printing system of this embodiment includes an information processing device 1 and a printing device 101. The information processing device 1 is capable of communicating with the printing device 101.

[0014] The printing device 101 of this embodiment is in the form of, for example, a label printer or label writer. That is, the print medium 110 of this embodiment is in the form of a long tape. The printing device 101 prints a label image 115 on the print medium 110 according to its intended use as a label. The label image 115 is printed on the print medium 110 along its length (hereinafter referred to as the "medium length direction"). Note that the print medium 110 may be in a form other than a long tape. When the printing device 101 acquires a print file indicating the label image 115 from the information processing device 1, it can print the label image 115 indicated by the print file on the print medium 110.

[0015] The print medium 110 on which the label images 115 are printed is automatically or manually cut for each label image 115. Each label is affixed to various objects, such as name tags, file spines, store price tags, mailing envelopes, industrial materials, fixtures, notebooks, signs, and the like.

[0016] The information processing device 1 can execute a label image creation application 5a (hereinafter abbreviated as "application 5a"). The application 5a is software including a computer program for realizing an image creation function. The image creation function includes generating a label image 115 based on a user operation and sending a print file representing the label image 115 to the printing device 101. The print file includes a converted LBX file (described later) and may also include a converted database file (described later) (see FIG. 11).

[0017] By using the app 5a, the user can create a new label image 115 via an editing screen (not shown). The user can also save the created label image 115, open and edit a saved label image 115, and issue a print instruction for the label image 115. A print instruction includes operating (e.g., clicking or tapping) the transfer button 24 on a transfer screen 20 (see FIG. 7 ), which will be described later. When a print instruction is issued, a print file for the specified label image 115 is sent to the printing device 101.

[0018] The information processing device 1 may communicate with the printing device 101 using any communication method. The information processing device 1 and the printing device 101 may, for example, be capable of wireless or wired communication with each other. Wireless communication methods may include, for example, wireless LAN and Bluetooth. "Bluetooth" is a registered trademark. Wired communication methods may include, for example, USB (Universal Serial Bus) and wired LAN. The information processing device 1 may be, for example, in the form of a desktop personal computer, or in the form of an easily portable so-called laptop computer, tablet, smartphone, or the like.

[0019] (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, a storage unit 5, and a communication unit 6. The control unit 2 includes a CPU 2a and a memory 2b. The CPU 2a as a processor executes processing in accordance with computer programs stored in the memory 2b and the storage unit 5. The memory 2b may include semiconductor memory such as a ROM, a RAM, an NVRAM, or a flash memory.

[0020] The storage unit 5 includes storage devices such as a solid state drive (SSD) and a hard disk drive (HDD), and stores various computer programs and data. In this 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. The storage unit 5 also stores the above-mentioned application 5a. In this embodiment, the OS, printer driver, and application 5a are installed in the information processing device 1 and used.

[0021] The application 5a may be stored in any manner in the storage unit 5. For example, the application 5a may be read into the information processing device 1 from a storage medium such as a CD, DVD, or USB memory and stored in the storage unit 5. Alternatively, the application 5a may be downloaded to the information processing device 1 from an external server or the like and stored in the storage unit 5. Alternatively, the application 5a may be pre-stored in the storage unit 5 when the information processing device 1 is shipped. In the following description, the entity that executes a program (for example, the control unit 2 in the information processing device 1) may be referred to simply by the program name or software name. For example, the description "the label image creation application 5a" or "the application 5a" may specifically mean "the control unit 2 that executes the label image creation application 5a."

[0022] The display unit 3 displays various screens to the user. An example of the display unit 3 is a liquid crystal display. Examples of the various screens include a home screen 10 (see FIG. 2), a transfer screen 20 (see FIG. 5), and a transfer candidate selection screen 50 (see FIG. 6), which will be described later.

[0023] The input unit 4 includes one or more input devices for receiving input operations from a user. Specifically, the input unit 4 may include, for example, a keyboard, a mouse, and / or a touch panel, or may include an input device of a different form.

[0024] The communication unit 6 performs wireless or wired communication with the communication unit 105 of the printing device 101 in accordance with the above-mentioned communication method. The above-mentioned print file is transmitted from the communication unit 6. (1-3) Printer configuration As shown in FIG. 1, the printing device 101 includes a control unit 102, a display unit 103, an input unit 104, a communication unit 105, and a printing unit 106.

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

[0026] The display unit 103 displays various information to the user operating the printing device 101. The input unit 104 accepts various input operations from the user. The communication unit 105 communicates with the communication unit 6 of the information processing device 1 by wireless or wired communication in accordance with the above-mentioned communication method. The communication unit 105 receives the above-mentioned print file.

[0027] The printing unit 106 prints a label image 115 on the print medium 110. The printing unit 106 prints an image using any of various printing methods, such as thermal transfer, direct thermal, or inkjet. In this embodiment, the printing unit 106 prints an image on the print medium 110 using, for example, thermal transfer. In this embodiment, the print medium 110 is provided in the form of a roll in which the print medium 110 is wound up. The print medium 110 is stored in a cassette (not shown). The cassette is detachably attached to the printing device 101.

[0028] When the control unit 102 receives a print file from the information processing device 1 via the communication unit 105, it causes the printing unit 106 to print the label image 115 indicated by the print file. The printing unit 106 prints the label image 115 on the print medium 110 while pulling the print medium 110 out of the cassette in accordance with various commands from the control unit 102.

[0029] (1-4) Home screen When the app 5a is started, it displays a home screen 10, as shown in Fig. 2, on the display unit 3. The user can perform various input operations starting from the home screen 10 to generate various label images 115 or edit label images 115 that have already been generated.

[0030] The home screen 10 includes a tab screen 11, a first tab 12a, a second tab 12b, and a transfer button 17. The content of the tab screen 11 corresponds to the selected one of the first tab 12a and the second tab 12b.

[0031] FIG. 2 illustrates an example in which the first tab 12a is selected and the tab screen 11 corresponding to the first tab 12a is displayed. The tab screen 11 corresponding to the first tab 12a displays a plurality of category icons 15. Each category icon 15 corresponds to a plurality of categories classified according to their intended use. Each category icon 15 is associated with a template of a label image 115 belonging to the corresponding category. When any category icon 15 is selected, a list of templates corresponding to that category icon 15 is displayed. When any template is selected, an editing screen is displayed on the display unit 3. The label image 115 of the selected template is displayed on the editing screen. The user can edit the label image 115 by inputting data into the editing screen. The created label image 115 can then be printed by the printing device 101. The created label image 115 can also be saved in the form of a label file, which will be described later.

[0032] When the second tab 12b is selected on the home screen 10, a tab screen 11 (not shown) corresponding to the second tab 12b is displayed. The tab screen corresponding to the second tab 12b displays a list of information about label images 115 that have been created and saved in the past. When any one of the label images 115 is selected from the list, an editing screen for that label image 115 to be edited is displayed.

[0033] When the transfer button 17 on the home screen 10 is operated (for example, clicked or tapped), a transfer screen 20 is displayed on the display unit 3. (1-5) Label images associated with the database As shown in Fig. 3, a label image 115 that can be created in this embodiment includes one or more objects. The label image 115 in Fig. 3 includes three objects, namely, a first object 121, a second object 122, and a third object 123. The user can freely decide where and what kind of objects to place.

[0034] A database may be associated with the label image 115. A database has one or more data fields (i.e., columns) and one or more records (i.e., rows). A link object may be placed on the label image 115 associated with a database. A link object is an object associated with a specific data field in a database (or one cell in that data field). A link object is an image (e.g., text) that shows the data of one of the cells in the link field, which is the data field associated with the link object.

[0035] FIG. 3 shows a database 130, which is an exemplary embodiment of a database. The label image 115 in FIG. 3 is associated with the database 130. The database 130 includes three data fields, namely, a first data field F1, a second data field F2, and a third data field F3. The database 130 also has three records, namely, a first record R1, a second record R2, and a third record R3. The database 130 further includes a first row R0. The first row R0 specifies the names of each data field. Note that the first row R0 may also be used as a record.

[0036] By way of example only, the first to third objects 121 to 123 in the label image 115 in Fig. 3 are all link objects associated with the database 130 in Fig. 3. In other words, the database 130 in Fig. 3 has link fields associated with the objects in the label image 115.

[0037] Specifically, the first object 121 is associated with a first data field F1, the second object 122 is associated with a second data field F2, and the third object 123 is associated with a third data field F3.

[0038] For example, the user can print a label image 115 in which the data "2019 / 04 / 25" of the cell of the first record R1 in the first data field F1 is displayed as the first object 121. Alternatively, for example, three label images 115 in which the data of the first to third records R1 to R3 are displayed respectively can be printed individually. The same applies to the second and third objects 122 and 123.

[0039] The label image 115 may not include a link object, or may contain a mixture of objects with no database associated therewith and link objects.

[0040] (1-6) Label image saving format When the application 5a receives an instruction to save the label image 115 created on the editing screen, it generates a label file indicating the created label image 115 and saves it in the storage unit 5. In this embodiment, the created label image 115 can be saved as a label file in either the standard format or the extended format exemplified in FIG.

[0041] A standard format label file includes an LBX file 56, but does not include a database file 57, which will be described later. The extension of the LBX file 56 is, for example, ".lbx." The LBX file 56 includes layout information. The layout information includes specific content of the label image 115, such as paper size information and an object list. The paper size information indicates the size of the print medium 110 on which the label image 115 is printed. The object list includes object information for each object included in the label image 115. The object information includes various information such as position, specific content (i.e., appearance, shape, pattern, color scheme, etc.), size, etc.

[0042] The extended format label file includes an SLBX file 55. The SLBX file 55 includes an LBX file 56 and a database file 57. The database file 57 includes a database associated with the LBX file 56 (specifically, its label image 115). In this embodiment, the database file 57 is a CSV file with the extension ".csv."

[0043] The SLBX file 55 is an LBX file 56 and a database file 57 integrated into a single file. Specifically, the SLBX file 55 is in the form of a compressed file in which the LBX file 56 and the database file 57 are compressed in a predetermined compression format. In this embodiment, the predetermined compression format is the ZIP format. The extension of the SLBX file 55 may be ".zip," which is the standard extension for the ZIP format, but in this embodiment, the extension is different from ".zip," for example, ".slbx," so that the user can easily recognize the file as an SLBX file 55.

[0044] In this way, in this embodiment, the label image 115 associated with a database can be managed together with the database as a single extended format label file. Note that various types of databases can be associated with the label image 115, but when the database is saved as an extended format label file, in this embodiment, the database file is converted to CSV format and saved.

[0045] The layout information of the LBX file 56 included in the SLBX file 55 may include information indicating a database (e.g., a database file name) in addition to the paper size information and object list described above. Furthermore, the object information corresponding to a link object in the object list further includes link information. The link information includes, for example, information indicating the link field with which the link object is associated.

[0046] Note that a label image 115 that is not associated with a database can also be saved as an extended format SLBX file 55. In this case, the SLBX file 55 does not include a database file 57. Hereinafter, a "first type extended label file" refers to an SLBX file 55 that includes a database file 57, and a "second type extended label file" refers to an SLBX file 55 that does not include a database file 57.

[0047] (1-7) Transferring print files When the transfer button 17 on the home screen 10 is operated (e.g., clicked or tapped), the app 5a displays a transfer screen 20 shown in FIG. 5 on the display unit 3. Using this transfer screen 20 as a starting point, the user can select a label image 115 that they want to print on the printing device 101 and transfer (i.e., send) the print file of that label image 115 to the printing device 101.

[0048] As shown in FIG. 5, the transfer screen 20 includes a candidate list display area 21, a reference button 22, transfer number information 23, and a transfer button 24. The candidate list display area 21 displays a transfer candidate list that lists candidates for label files (hereinafter referred to as "transfer candidate files") that you want to transfer to the printing device 101 and print. Figure 5 shows a state in which no files have yet been selected in the transfer candidate list.

[0049] The transfer number information 23 indicates the total number of transfer candidate files listed in the transfer candidate list. In detail, when a transfer candidate file is a first-class extended label file, the transfer number information 23 counts the LBX file 56 and the database file 57 included in the first-class extended label file individually.

[0050] The user can select a transfer candidate file by operating (e.g., clicking, tapping, etc.) the browse button 22. When the browse button 22 is operated, the application 5a displays a transfer candidate selection screen 50, an example of which is shown in FIG. 6, on the display unit 3. The transfer candidate selection screen 50 includes a saved file list area 51, a file name box 52, and an open button 53. The saved file list area 51 displays a list of file information for files saved in the selected folder. The file information includes the file name, update date and time, type, etc.

[0051] Note that Figure 6 is set up so that only files related to label files among those saved in the selected folder are displayed. In Figure 6, files with the file type "LBX file" are standard format label files. Files with the file type "SLBX file" are extended format label files. Files with the file type "CSV file" are database files.

[0052] The user can select a transfer candidate file from among the files displayed on the transfer candidate selection screen 50. A transfer candidate file can be specified, for example, by clicking or tapping on the corresponding file information. When the file information of any file is selected, the selected file information is highlighted (for example, the background color is changed), and the file name of the selected file is displayed in the file name box 52.

[0053] When the Open button 53 is operated (e.g., clicked or tapped) while any file is selected, the application 5a displays the transfer screen 20 again on the display unit 3. At this time, the application 5a adds the transfer candidate file selected on the transfer candidate selection screen 50 to the transfer candidate list. Specifically, the application 5a adds candidate file information indicating the selected transfer candidate file to the transfer candidate list. At this time, if the selected transfer candidate file is an extended format label file, the application 5a decompresses the label file and acquires the LBX file 56 included in the label file. If the label file is a first-type extended label file, the application 5a also acquires the database file 57. Adding a first-type extended label file to the transfer candidate list means adding the LBX file 56 and the database file 57 obtained by decompressing the label file to the transfer candidate list all at once.

[0054] When no transfer candidate files are selected and "Layout1.slbx" is selected on the transfer candidate selection screen 50, this "Layout1.slbx" is decompressed to obtain the LBX file 56 and database file 57. Then, the candidate file information 31 (see FIG. 7) for "Layout1.slbx" is displayed in the transfer candidate list.

[0055] If there are other files besides "Layout1.slbx" that the user wants to transfer to the printing device 101, the user can operate the browse button 22 to display the transfer candidate selection screen 50 again and select the files they want to transfer. By repeating this operation, the user can select as many transfer candidate files as desired. Then, the candidate file information for each selected transfer candidate file is listed on the transfer screen 20.

[0056] 7 shows the state in which "Layout1.slbx," "Layout2.slbx," and "Layout3.lbx" have been selected as transfer candidate files, and candidate file information 31, 32, and 33 for each of these three transfer candidate files has been listed. Note that "Layout2.slbx" is a first-class extended label file, and "Layout3.lbx" is a standard format label file.

[0057] In this embodiment, the candidate file information is displayed in an expander format. The expander format is a display format that can be alternately switched between a non-expanded state and an expanded state. In the non-expanded state, only simple information is displayed as the candidate file information. On the other hand, in the expanded state, more information is displayed as the candidate file information than in the non-expanded state. FIG. 7 illustrates the non-expanded state, and FIG. 8 illustrates the expanded state.

[0058] 7, the candidate file information in the non-expanded state includes, for example, the file name of the transfer candidate file, a zoom button 26, and a delete button 27. Each time the zoom button 26 is operated (e.g., clicked or tapped), the non-expanded state and the expanded state are alternately switched.

[0059] For example, when the enlargement / reduction button 26 of the candidate file information 31 of "Layout1.slbx" is operated in the state of FIG. 7, the candidate file information 31 is switched to an expanded state as shown in FIG.

[0060] Similarly, when the zoom button 26 for the candidate file information 32 for "Layout2.slbx" is operated in the state of Fig. 7, the candidate file information 32 switches to the expanded state shown in Fig. 8. Also, when the zoom button 26 for the candidate file information 33 for "Layout3.lbx" is operated in the state of Fig. 7, the candidate file information 33 switches to the expanded state shown in Fig. 8. When the zoom button 26 is operated in the expanded state, the candidate file information 33 switches to the non-expanded state.

[0061] 7 shows an example in which all three pieces of candidate file information 31 to 33 are in a non-expanded state, and Fig. 8 shows an example in which all three pieces of candidate file information 31 to 33 are in an expanded state. However, by operating the expand / contract button 26 individually, each piece of listed candidate file information can be individually displayed in an expanded or non-expanded state.

[0062] As illustrated in Figure 8, the candidate file information in the expanded state includes the file name, zoom button 26, and delete button 27 that were also displayed in the unexpanded state, as well as file detail information 36, which is more detailed information about the transfer candidate file.

[0063] Specifically, when the transfer candidate file is a first-type extended label file, the file detail information 36 includes LBX detail information 36a and database detail information 36b. The LBX detail information 36a is information about the LBX file 56 included in the first-type extended label file. The database detail information 36b is information about the database file 57 included in the first-type extended label file.

[0064] In this embodiment, both the LBX detailed information 36a and the database detailed information 36b include the transfer name, size, type, file path, etc. of the relevant file. Note that "layout" in "type" indicates that it is an LBX file 56. The "transfer name" is the file name when actually transferred to the printing device 101. The user can change the transfer name individually for each file. Note that the transfer name displayed by default is the original file name as it was displayed on the transfer candidate selection screen 50.

[0065] 8, since "Layout1.slbx" is a first-type extended label file, the file detail information 36 includes LBX detail information 36a and database detail information 36b. On the other hand, since "Layout2.slbx" is a second-type extended label file, the file detail information 36 includes LBX detail information 36a but does not include database detail information 36b. Also, since "Layout3.lbx" is a standard format label file, the file detail information 36 includes LBX detail information 36a but does not include database detail information 36b.

[0066] In either the expanded state or the unexpanded state, when the delete button 27 of any transfer candidate file is operated, that transfer candidate file is deleted from the candidate list display area 21, that is, excluded from the transfer candidates. When the delete button 27 of a first type extended label file is operated, the LBX file 56 and the database file 57 included in that first type extended label file are deleted collectively from the candidate list display area 21.

[0067] The user can individually set the transfer candidate files listed in the transfer candidate list to a selected state or an unselected state. In the present embodiment, when a transfer candidate file selected on the transfer candidate selection screen 50 is first displayed in the transfer candidate list, it is set to an unselected state. When a predetermined selection operation (e.g., clicking or tapping on an area displaying the corresponding candidate file information) is performed on an unselected transfer candidate file, the application 5a sets the transfer candidate file to a selected state. Conversely, when a selection operation is performed on a transfer candidate file that has already been set to a selected state, the application 5a sets the transfer candidate file to an unselected state. Candidate file information in a selected state is displayed in a different manner from when it is unselected. For example, the background color of selected candidate file information may be changed from that of the unselected state.

[0068] When the transfer button 24 is operated with one or more of the listed transfer candidate files selected, the application 5a transfers the selected transfer candidate files to the printing device 101 as the print files described above. This makes it possible to print the label image 115 indicated by the transferred transfer candidate files. Note that the transfer candidate files are converted into a specific file format (i.e., the converted LBX file and / or the converted database file described above) that can be processed by the printing device 101, as will be described in detail later, and then transferred.

[0069] (1-8) Transfer control process The transfer control process executed by the control unit 2 (more specifically, the CPU 2a) of the information processing device 1 to realize the above-mentioned various functions via the transfer screen 20 will be described with reference to Fig. 9. The transfer control process is realized by executing a program corresponding to the transfer control process, which is included in the label image creation application 5a. The control unit 2 executes the transfer control process while the transfer screen 20 is displayed on the display unit 3.

[0070] When the control unit 2 starts the transfer control process, in S110, it determines whether a list addition operation has been performed. The list addition operation is a user operation for adding a transfer candidate file to the transfer candidate list on the transfer screen 20. In detail, the list addition operation includes operating the browse button 22 on the transfer screen 20, and selecting a transfer candidate file on the transfer candidate selection screen 50 ( FIG. 6 ) displayed by operating the browse button 22 and operating the open button 53. Note that when the browse button 22 on the transfer screen 20 is operated, the control unit 2 temporarily transitions to the transfer candidate selection screen 50, and then when the open button 53 is operated, the control unit 2 displays the transfer screen 20 again, although the illustration of the screen transition process is omitted in FIG. 9.

[0071] If a list addition operation is performed in S110, the process proceeds to S120. In S120, the control unit 2 determines whether the selected transfer candidate file is an SLBX file 55 (i.e., a first-type extended label file or a second-type extended label file). If the transfer candidate file is an SLBX file 55, the process proceeds to S130. In S130, the control unit 2 executes a decompression process. Specifically, the selected SLBX file 55 is decompressed. As a result, the LBX file 56 contained in the SLBX file 55 is obtained. If the SLBX file 55 includes a database file 57, the database file 57 is also obtained.

[0072] In this embodiment, the decompression process is performed in a temporary folder set in the storage unit 5, and the LBX file 56 and database file 57 obtained by the decompression process are also saved in the temporary folder. The temporary folder is a folder that is temporarily used for the decompression process. In this embodiment, the temporary folder is, for example, a folder that is managed by the OS as a so-called hidden folder.

[0073] In S140, the control unit 2 acquires LBX file information from the LBX file 56 obtained in S130. The LBX file information includes various information related to the LBX file 56 (for example, file name, file size, file path, etc.).

[0074] In S150, the control unit 2 determines whether or not the database file 57 has been obtained by the decompression process in S130. If the database file 57 has not been obtained (i.e., the transfer candidate file is a second-type extended label file), the process proceeds to S170. If the database file 57 has been obtained, the process proceeds to S160.

[0075] In S160, the control unit 2 acquires database file information from the obtained database file 57. The database file information includes various information related to the database file 57 (for example, file name, file size, file path, etc.).

[0076] In S170, the control unit 2 adds the SLBX file 55 to be added (i.e., selected as a transfer candidate file in S110) to the transfer candidate list on the transfer screen 20. Specifically, the candidate file information for the SLBX file 55 is displayed in an expander format. Candidate file information 31 in FIG. 7 is an example of the result of performing the process of S170 on a first-type extended label file. Candidate file information 32 in FIG. 7 is an example of the result of performing the process of S170 on a second-type extended label file.

[0077] 9, "EXP format" is an abbreviation for expander format. In this embodiment, when a device is added to the transfer candidate list for the first time, it is displayed in a non-expanded state (see FIG. 7). However, when a device is added for the first time, it may be displayed in an expanded state (see FIG. 8). After the process of S170, the process proceeds to S110.

[0078] If the transfer candidate file is not an SLBX file 55 in S120 (i.e., it is a standard format label file), the process proceeds to S180. In S180, the control unit 2 acquires LBX file information from the transfer candidate file. Then, in the following S190, the control unit 2 adds the LBX file 56 to be added (i.e., selected as the transfer candidate file in S110) to the transfer candidate list. Specifically, the candidate file information for the LBX file 56 is displayed in expander format. The candidate file information 33 in Figure 7 is an example of the result of performing the process of S190 on a standard format label file. After the process of S190, the process proceeds to S110.

[0079] If a list addition operation has not been performed in S110, the process proceeds to S200. In S200, the control unit 2 determines whether a selection operation has been performed on any of the listed transfer candidate files. If a selection operation has not been performed, the process proceeds to S220. If a selection operation has been performed, the process proceeds to S210. In S210, the control unit 2 executes operation response processing. Specifically, if a selection operation has been performed on a transfer candidate file that is in an unselected state, the control unit 2 sets the transfer candidate file to a selected state, and if a selection operation has been performed on a transfer candidate file that is in a selected state, the control unit 2 sets the transfer candidate file to an unselected state.

[0080] In S220, the control unit 2 determines whether a delete operation has been performed on any of the listed transfer candidate files. A delete operation includes operating the delete button 27 (see FIGS. 7 and 8). If a delete operation has not been performed, the process proceeds to S240. If a delete operation has been performed, the process proceeds to S230. In S230, the control unit 2 executes the delete process. Specifically, the transfer candidate file on which the delete operation has been performed is deleted from the transfer candidate list.

[0081] In S240, the control unit 2 determines whether a resizing operation has been performed on any of the listed transfer candidate files. The resizing operation includes operating the resizing button 26 (see FIGS. 7 and 8). If a resizing operation has not been performed, the process proceeds to S260. If a resizing operation has been performed, the process proceeds to S250. In S250, the control unit 2 executes the resizing process. Specifically, if a resizing operation has been performed on a transfer candidate file in an unexpanded state, the transfer candidate file is displayed in an expanded state. On the other hand, if a resizing operation has been performed on a transfer candidate file in an expanded state, the transfer candidate file is displayed in an unexpanded state.

[0082] In S260, the control unit 2 determines whether a transfer instruction has been issued. A transfer instruction includes operating the transfer button 24 on the transfer screen 20. If a transfer instruction has not been issued, the process proceeds to S110. If a transfer instruction has been issued, the process proceeds to S270. In S270, the control unit 2 executes the transfer process. Details of the transfer process are as shown in FIG. 10.

[0083] When the control unit 2 shifts to the transfer process, in S310 it selects one transfer candidate file from the transfer candidate list as a file to be processed. In S320, the control unit 2 determines whether the transfer candidate file to be processed is an SLBX file 55. If the transfer candidate file to be processed is an SLBX file 55, the process proceeds to S330. In S330, the control unit 2 converts the LBX file 56 obtained in the process of S130 in the SLBX file 55 to be processed into the specific file format described above. This generates a converted LBX file.

[0084] In S340, the control unit 2 determines whether the conversion in S330 was successful. If the conversion in S330 was not performed normally (i.e., if the conversion failed), the process proceeds to S410. In S410, the control unit 2 executes error processing. Specifically, for example, a message indicating that the conversion failed is displayed on the display unit 3. Then, subsequent processing for the transfer candidate file to be processed is stopped, and the process proceeds to S400. In other words, transfer candidate files for which the conversion in S330 failed are not transferred to the printing device 101.

[0085] If it is determined in S340 that the conversion in S330 was successful, the process proceeds to S350. In S350, the control unit 2 adds the converted LBX file created in S330 to the transfer file list. The transfer file list stores files to be transferred to the printing device 101.

[0086] In S360, the control unit 2 determines whether the SLBX file 55 to be processed includes a database file 57. If the database file 57 is not included, the process proceeds to S400. If the database file 57 is included, the process proceeds to S370.

[0087] In S370, the control unit 2 converts the database file 57 into the specific file format described above, thereby generating a converted database file. In S380, the control unit 2 determines whether the conversion in S370 was successful. If the conversion in S370 was not successful, the process proceeds to S410. If the conversion in S370 was successful, the process proceeds to S390. In S390, the control unit 2 adds the converted database file generated in S370 to the transfer file list.

[0088] In S320, if the transfer candidate file to be processed is not an SLBX file 55 (i.e., it is a standard format LBX file 56), the process proceeds to S420. In S420, the control unit 2 converts the LBX file 56 to be processed into the specific file format described above. This generates a converted LBX file.

[0089] In S430, the control unit 2 adds the converted LBX file created in S420 to the transfer file list. After processing S430, the process returns to S400. Note that after processing S420, the same process as S340 may be executed on the processing result. If the conversion in S420 fails, the process may return to S410.

[0090] In S400, the control unit 2 determines whether or not there are any unprocessed transfer candidate files remaining in the transfer candidate list. "Unprocessed" means that the file has not yet been selected as a target for processing in S310. If there are any unprocessed transfer candidate files remaining, the process proceeds to S310. If there are no unprocessed transfer candidate files, the process proceeds to S510 (see FIG. 11).

[0091] In S510, the control unit 2 sets the converted file of one transfer candidate file from the transfer file list as the transfer target. Specifically, if the transfer candidate file set as the transfer target is a first-class extended label file, a converted LBX file and a converted database file have been generated as converted files, so these two are set as the transfer target. If the transfer candidate file set as the transfer target is a second-class extended label file or a standard format label file, a converted LBX file has been generated as the converted file, so this is set as the transfer target.

[0092] In S520, the control unit 2 transfers to the printing device 101 the converted LBX file that was set as the transfer target in S510. In S530, the control unit 2 determines whether the transfer in S520 was successful. If the transfer in S520 was not performed normally (i.e., if the transfer failed), the process proceeds to S580. In S580, the control unit 2 executes error processing. Specifically, for example, a message indicating that the transfer failed is displayed on the display unit 3. Then, further processing is stopped for the transfer candidate file currently being transferred, and the process proceeds to S590. In other words, for a transfer candidate file for which the transfer of the converted LBX file failed, the converted database file will not be transferred even if a converted database file remains.

[0093] The determination in S530 may be performed in any manner. For example, the printing device 101 may be configured to set its own communication status to "receiving" when the converted LBX file is received, to set the communication status to "normal" if the reception is completed successfully, and to set the communication status to "abnormal" if the reception is unsuccessful. Meanwhile, the application 5a may monitor the communication status of the printing device 101 after transferring the converted LBX file. It may determine that the transfer is successful if the communication status changes from "receiving" to "normal." Conversely, it may determine that the transfer is unsuccessful if the status changes to "abnormal." Alternatively, the printing device 101 may be configured to send a reception completion notification to the information processing device 1 when the reception of the converted LBX file is completed successfully. The application 5a may determine that the transfer is successful if it receives a reception completion notification within a predetermined time after transferring the converted LBX file, and determine that the transfer is unsuccessful if it does not receive a reception completion notification within the predetermined time.

[0094] If it is determined at S530 that the transfer at S520 was successful, the process proceeds to S540. At S540, the control unit 2 determines whether the converted database file is included in the transfer target. If the converted database file is not included in the transfer target, the process proceeds to S590. If the converted database file is included in the transfer target, the process proceeds to S550.

[0095] In S550, the control unit 2 transfers the converted database file to the printing device 101. In S560, the control unit 2 determines whether the transfer in S550 was successful. If the transfer in S550 was not successful, the process proceeds to S580. If the transfer in S550 was successful, the process proceeds to S590.

[0096] In S590, the control unit 2 determines whether or not there are any unprocessed transfer candidate files remaining in the transfer file list. "Unprocessed" here means that the file has not yet been selected as a transfer target in S510. If there are any unprocessed transfer candidate files remaining, the process proceeds to S510. If there are no unprocessed transfer candidate files, the process proceeds to S600. In S600, the transfer results are displayed on the display unit 3. That is, for each transfer candidate file stored in the transfer file list, information indicating whether the transfer was successful or not is displayed.

[0097] (1-9) Effects of the embodiment In the embodiment described above, when a first-class extended label file is selected as a transfer candidate, the application 5a displays candidate file information 31 indicating the LBX file 56 and the database file 57 included in the first-class extended label file (FIG. 8). This allows the user to easily select the LBX file 56 and the associated database file 57 and transfer them to the printing device 101.

[0098] Moreover, the candidate file information 31 is displayed in an expander format (FIGS. 7 and 8), so that the user can easily check, as needed, whether the selected transfer candidate file includes a database file 57 or not.

[0099] Furthermore, when a transfer candidate file is transferred to the printing device 101, the transfer candidate file is converted into a specific file format (FIG. 10). If the transfer candidate file is a first-class extended label file, the LBX file 56 and the database file 57 are converted. In this case, if conversion of the first one (LBX file 56 in this embodiment) fails, conversion of the other (database file 57 in this embodiment) is not performed, and the first-class extended label file is excluded from the transfer candidates.

[0100] Furthermore, when transferring a converted LBX file or a converted database file, if the first transfer (in this embodiment, the converted LBX file) fails, the other (in this embodiment, the converted database file) will not be transferred.

[0101] This prevents an incomplete transfer, such as transferring only one of the converted LBX file and the converted database file, and prevents the printing device 101 from printing an unintended label image.

[0102] (1-10) Correspondence of words The label image creation application 5a corresponds to an example of an image processing program in the present disclosure. The LBX file 56 included in the SLBX file 55 including the database file 57 corresponds to an example of a first image file in the present disclosure, and the label image indicated by the LBX file 56 corresponds to an example of a first print image in the present disclosure. The LBX file 56 included in the SLBX file 55 not including the database file 57 corresponds to an example of a second image file in the present disclosure, and the label image indicated by the LBX file 56 corresponds to an example of a second print image in the present disclosure. The LBX file 56 included in the standard format label file corresponds to an example of a third image file in the present disclosure, and the label image indicated by the LBX file 56 corresponds to an example of a third print image in the present disclosure. The first type extended label file corresponds to an example of a first type extended image file in the present disclosure. The second type extended label file corresponds to an example of a second type extended image file in the present disclosure. The transfer screen 20 corresponds to an example of a list screen in the present disclosure. In the transfer screen 20 of Figure 8, the LBX detailed information 36a and database detailed information 36b included in the candidate file information 31 correspond to an example of the first file information and database information in the present disclosure, the LBX detailed information 36a included in the candidate file information 32 corresponds to an example of the second file information in the present disclosure, and the LBX detailed information 36a included in the candidate file information 33 corresponds to an example of the third file information in the present disclosure.

[0103] S170 and S250 correspond to an example of the display process in the present disclosure. S330 and S370 correspond to an example of the file conversion process in the present disclosure. 2. 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.

[0104] (2-1) As the candidate file information 31 (FIGS. 7 and 8), any specific information may be displayed in each of the unexpanded and expanded states. For example, in the unexpanded state, the file name is displayed as shown in FIG. 7, but information other than the file name may be displayed instead of or in addition to the file name. In the expanded state, other information may be displayed instead of or in addition to at least one of the transfer name, size, type, and file path shown in FIG. 8.

[0105] (2-2) In the above embodiment, immediately after a transfer candidate file is selected, the transfer screen 20 displays the candidate file information of the selected transfer candidate file in an unexpanded state (FIG. 7), but it may also be displayed in an expanded state from the beginning (FIG. 8).

[0106] (2-3) The present disclosure is not limited to application to the printing device 101 in the form of a label printer. The present disclosure is applicable to various printing devices in forms other than label printers. (2-4) 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. [Explanation of symbols]

[0107] 1...information processing device, 2...control unit, 2a...CPU, 2b...memory, 3...display unit, 4...input unit, 5...storage unit, 5a...label image creation application, 6...communication unit, 10...home screen, 17, 24...transfer button, 20...transfer screen, 26...zoom button, 27...delete button, 31, 32, 33...candidate file information, 36a...LBX detailed information, 36b...database detailed information, 50...transfer candidate selection screen, 53...button, 55...SLBX file, 56...LBX file, 57...database file, 101...printing device, 115...label image.

Claims

1. An image processing program executable by a control unit in an information processing device including a storage unit, a display unit, a communication unit capable of communicating with a printing device, and a control unit, the storage unit is capable of storing a first type extended image file in which a first image file and a database file are compressed in a predetermined compression format, the database file indicates a database, the first image file indicates a first print image that can be printed by the printing device, and the first print image includes an object associated with specific data in the database and indicating the data; The image processing program causes the control unit to a display process for displaying, on the display unit, first file information indicating the first image file and database information indicating the database file in association with each other in response to the first type extended image file being selected as a candidate for transfer to the printing device; a transfer process of transferring the first image file and the database file to the printing device through the communication unit in response to receiving an instruction to transfer the first type extended image file after the display process is executed; An image processing program that executes the following:

2. 2. The image processing program according to claim 1, the display process displays the first type extended image file in an expander format; The display in the expander format is as follows: a non-expanded state in which the first file information and the database information are not displayed; an expanded state displaying the first file information and the database information; and switching the display mode in response to a user instruction. Image processing program.

3. 2. The image processing program according to claim 1, the display process includes displaying a list screen on the display unit that lists the files selected as the transfer candidates, and adding the first file information and the database information to the list screen in response to the selection of the first type extended image file; The image processing program causes the control unit to a deletion process in which, in response to an instruction to delete the first type extended image file listed on the list screen, the first file information and the database information are deleted from the list screen all at once; An image processing program that executes the following:

4. 2. The image processing program according to claim 1, The control unit a decompression process in which, in response to the first type extended image file being selected as the transfer candidate, the first type extended image file is decompressed and the first image file and the database file are saved in a predetermined folder in the storage unit; Execute the display process displays the first file information and the database information of the first image file and the database file stored in the folder by the decompression process in response to the first type extended image file being selected as the transfer candidate. Image processing program.

5. 5. The image processing program according to claim 4, The storage unit is capable of storing a second type extended image file obtained by compressing a second image file in the predetermined compression format, and the second image file represents a second print image that can be printed by the printing device. the decompression process decompresses the second type extended image file in the predetermined folder and saves the second image file in response to the second type extended image file being selected as the transfer candidate; the display process displays, on the display unit, second file information indicating the second image file stored in the folder by the decompression process in response to the second type extended image file being selected as the transfer candidate; the transfer process transfers the second type extended image file to the printing device in response to receiving an instruction to transfer the second type extended image file after the display process is executed. Image processing program.

6. 2. The image processing program according to claim 1, the storage unit is capable of storing a third image file in a file format different from the first type extended image file, the third image file representing a third print image that can be printed by the printing device; the display process displays third file information indicating the third image file on the display unit in response to the third image file being selected as the transfer candidate; the transfer process transfers the third image file to the printing device in response to receiving an instruction to transfer the third image file after the display process is executed. Image processing program.

7. 2. The image processing program according to claim 1, The control unit a file conversion process for converting the first image file and the database file into specific file formats that can be processed by the printing device after the display process is executed; Execute the transfer process transfers the converted first image file and the converted database file to the printing device when the file conversion process has successfully completed conversion of both the first image file and the database file; Image processing program.

8. 8. The image processing program according to claim 7, In the transfer process, if the conversion of either the first image file or the database file by the file conversion process is not completed normally, neither the first image file nor the database file converted by the file conversion process is transferred to the printing device. Image processing program.

9. 2. The image processing program according to claim 1, the transfer process transfers the first image file and the database file one by one to the printing device in order, and if the transfer of the first one of the first image file and the database file is not completed successfully, the transfer of the other one is not performed. Image processing program.

10. An information processing device including a storage unit, a display unit, a communication unit capable of communicating with a printing device, and a control unit, the storage unit is capable of storing an extended image file in which an image file and a database file are compressed in a predetermined compression format, the database file indicates a database, the image file indicates a print image that can be printed by the printing device, and the print image includes an object associated with specific data in the database and indicating the data; The control unit a display process for displaying, on the display unit, image file information indicating the image file and database information indicating the database file in association with each other, in response to the extended image file being selected as a candidate for transfer to the printing device; a transfer process of transferring the image file and the database file to the printing device through the communication unit in response to receiving an instruction to transfer the extended image file after the display process is executed; An information processing device configured to execute the above.

Images