Screen control device and screen control method
Patent Information
- Application Number
- JP2024075272
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-05-07
- Publication Date
- 2025-03-14
Smart Images
Figure 2025036068000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a screen control device and a screen control method for controlling a plurality of screens. [Background technology]
[0002] Conventionally, there is known a technique for simultaneously displaying an inactive preview screen and an active screen such as an input screen in screen control. Patent Document 1 discloses a technique for putting the download source browser screen into an input exclusive state and always displaying the preview screen in front of the download source browser screen when the download source browser screen and the preview screen are separate processes. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2008-293148 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, when the preview screen is displayed overlapping the input screen on which the user performs input, it may be difficult to check the input screen, and input may be difficult on the input screen. In addition, the topmost screen is generally in an active state where input is possible, but when a preview screen is arranged on the topmost screen, it is difficult to input information on the input screen arranged on the lower screen. For example, it is difficult to input information into an input area on the input screen while checking the actual situation using a preview screen including an image captured by a camera.
[0005] The present disclosure provides a screen control device and a screen control method that allow easy input of information into an input area while displaying a preview screen including a captured image. [Means for solving the problem]
[0006] One aspect of the present disclosure is a mobile terminal having a camera that captures an image of a subject including a code, a display device, and a processor, wherein when a predetermined application is launched by the processor, an input screen is displayed on the display device, and a preview screen of the subject is displayed in front of the input screen, while the display device is activated to allow input into an input area of the input screen, and the preview screen is continued to be displayed in front of the input screen until the code is successfully read. Effect of the Invention
[0007] According to the present disclosure, a screen control device and a screen control method are provided that can easily input information into an input area while displaying a preview screen including a captured image. [Brief description of the drawings]
[0008] [Figure 1] FIG. 1 is a front view showing a configuration example of a code reader device according to an embodiment of the present disclosure. [Diagram 2] FIG. 1 is a rear view showing a configuration example of a code reader device; [Diagram 3] FIG. 1 is a left side view showing a configuration example of a code reader device. [Figure 4] FIG. 1 is a right side view showing a configuration example of a code reader device. [Diagram 5] Functional block diagram of the code reader device [Figure 6] FIG. 13 is a diagram showing screen transitions on a display device of a code reader device and their explanations; [Figure 7] FIG. 11 is a diagram showing a control flow by a code reader device according to a first screen control example. [Figure 8] FIG. 11 is a diagram showing a screen transition by a code reader device according to a first screen control example. [Figure 9] FIG. 11 is a diagram showing a control flow by the code reader device according to the second screen control example. [Figure 10] FIG. 13 is a diagram showing a screen transition by a code reader device according to a second screen control example. [Figure 11]FIG. 11 is a diagram showing a control flow by a code reader device according to a third screen control example. [Figure 12] FIG. 13 is a diagram showing a screen transition by a code reader device according to a third screen control example. [Figure 13A] FIG. 13 is a diagram showing a control flow at a first timing by a code reader device according to a fourth screen control example. [Figure 13B] FIG. 13 is a diagram showing a control flow at a second timing by a code reader device according to a fourth screen control example. [Figure 14] FIG. 13 is a diagram showing a screen transition by a code reader device according to a fourth screen control example. [Figure 15] FIG. 13 is a diagram showing a control flow by a code reader device according to a fifth screen control example. [Figure 16] FIG. 13 is a diagram showing a screen transition by a code reader device according to a fifth screen control example. [Figure 17] FIG. 13 is a conceptual diagram showing a state of screen overlap in a code reader device. [Figure 18] FIG. 13 is a diagram showing an example of a screen displayed by a code reader device; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] Hereinafter, the embodiments will be described in detail with reference to the drawings as appropriate. However, more detailed explanation than necessary may be omitted. For example, detailed explanation of already well-known matters or duplicate explanation of substantially the same configuration may be omitted. This is to avoid the following explanation becoming unnecessarily redundant and to facilitate understanding by those skilled in the art. Note that the attached drawings and the following description are provided to enable those skilled in the art to fully understand the present disclosure, and are not intended to limit the subject matter described in the claims.
[0010] <Code reader device configuration> Fig. 1 is a front view showing a configuration example of a code reader device according to an embodiment of the present disclosure. Fig. 2 is a rear view showing the configuration example of a code reader device. Fig. 3 is a left side view showing the configuration example of a code reader device. Fig. 4 is a right side view showing the configuration example of a code reader device.
[0011] The code reader device 10 is, for example, a portable mobile terminal. The code reader device 10 captures an image of a subject including a code using a camera, and reads the code by performing image processing on the captured image (captured image). The code is, for example, a barcode, a two-dimensional code (for example, a QR code (registered trademark)), or other codes. The code is, for example, attached to a slip attached to a package or other object. The code may be displayed, for example, by printing on a paper medium or displaying on an electronic medium. The code reader device 10 displays multiple screens including a screen including the captured image, and assists in reading the code. The code reader device 10 has a housing that defines the outer shape, and includes various devices within the housing.
[0012] 1, the code reader device 10 includes, on the front side (front surface), a front camera 12A as the camera 12, a touch panel 13A, and a function switch 13B. The function switch 13B is a switch for executing a predetermined process to realize an arbitrary function. The code reader device 10 may also include, on the front side (front surface), a speaker, an illuminance sensor, a proximity sensor, a microphone, and the like.
[0013] 2, the code reader device 10 is provided with a rear camera 12B on the back surface (rear surface) as the camera 12. The code reader device 10 may also be provided with a microphone, a light source, and the like on the back surface (rear surface).
[0014] 3, the code reader device 10 has a function switch 13C on one side (for example, the left side). The function switch 13C is a switch for executing a predetermined process to realize an arbitrary function. The code reader device 10 may also have a volume adjustment button or the like on one side (for example, the left side).
[0015] 4, the code reader device 10 has a function switch 13D on the other side (for example, the right side). The function switch 13D is a switch for executing a predetermined process to realize an arbitrary function. The code reader device 10 may also have a port for inserting and removing a memory, a camera shutter, and the like on the other side (for example, the right side).
[0016] The function switch 13C includes a read start instruction switch 13R that instructs the start of reading a code. Instead of the function switch 13C including the read start instruction switch 13R, another input device 13 (e.g., function switch 13B or function switch 13D) may include the read start instruction switch 13R. The read start instruction switch 13R may be switched on and off, for example, each time it is pressed. Also, the read start instruction switch 13R may be turned on while it is pressed and turned off while it is not pressed, that is, when the press is released.
[0017] The code reader device 10 does not have a physical code reader module, and can read codes by image processing. Therefore, the code reader device 10 is thin and can be easily put in, for example, a pocket.
[0018] 5 is a block diagram showing an example of the functional configuration of the code reader device 10. The code reader device 10 includes a processor 11, a camera 12, an input device 13, a display device 14, and a memory 15. Note that the input device 13 and the display device 14 may be integrated into one device, such as a touch panel 13A.
[0019] The processor 11 may be configured using, for example, a Central Processing Unit (CPU) or a Digital Signal Processor (DSP). The processor 11 may be configured using various integrated circuits (for example, a Large Scale Integration (LSI) or a Field Programmable Gate Array (FPGA)). The processor 11 realizes various functions by executing programs stored in the memory 15. The processor 11 comprehensively controls each part of the code reader device 10 and performs various processes.
[0020] For example, the processor 11 obtains an image (captured image) of a subject captured by the camera 12 from the camera 12. The subject includes a code. The processor 11 extracts the code from the captured image. The processor 11 performs image processing on the code to read the contents of the code, that is, has a code reader function. The processor 11 may input the contents of the read code (reading result) into an input area (e.g., an input field) of a predetermined application (also simply described as an "app"). The predetermined application may include a search application, a package delivery application, and the like. The processor 11 also controls multiple screens and controls the display of the multiple screens. The multiple screens include an input screen 100 and a preview screen 110, which will be described later. Details of the screen control by the processor 11 will be described later. The processor 11 may control the validity of input to multiple screens arranged in a superimposed manner. The processor 11 may control the hierarchical relationship of the multiple screens when displayed (i.e., which screen is arranged in the upper layer (front side) and which screen is arranged in the lower layer (back side)).
[0021] For example, the processor 11 controls the operation mode. The operation modes include a normal reading mode, a continuous reading mode, a movement mode, and a semi-transparent mode. The normal reading mode is a mode in which one code is read in response to an instruction to start reading the code. The continuous reading mode is a mode in which a plurality of codes are continuously read in response to an instruction to start reading the codes. The movement mode is a mode in which the input screen 100 is made visible by moving or reducing the preview screen 110. The semi-transparent mode is a mode in which a screen (e.g., the input screen 100) arranged below the preview screen 110 is made visible by making the display of the preview screen 110 semi-transparent. The processor 11 may set one of the operation modes in response to an input operation on the input device 13, for example.
[0022] The camera 12 is configured to have at least a lens (not shown) and an image sensor (not shown). The image sensor is, for example, a solid-state imaging element such as a Charged-Coupled Device (CCD) or a Complementary Metal-Oxide-Semiconductor (CMOS), and converts an optical image formed on an imaging surface into an electrical signal. The camera 12 includes a front camera 12A and a rear camera 12B. The camera 12 captures an image of a subject. The subject may include a code. The code is provided, for example, by printing or attaching to the subject.
[0023] The input device 13 may include various buttons, keys, a keyboard, a mouse, a touch panel, a microphone, or other input devices. The input device 13 accepts input of various data or information. The input device 13 is operated, for example, by a user who uses the code reader device 10. The input device 13 includes a touch panel 13A (FIG. 1) arranged on the front surface, a function switch 13B (FIG. 1) arranged on the front surface, a function switch 13C (FIG. 3) arranged on the left side surface, a function switch 13D (FIG. 4) arranged on the right side surface, and the like.
[0024] The display device 14 is configured using a display such as a liquid crystal display (LCD) or an organic electroluminescence (EL) display, etc. The display device 14 displays various types of data or information.
[0025] The display device 14 displays a plurality of screens. For example, the display device 14 displays a screen of a predetermined application. The screen of the application includes an input screen 100 (an example of a second screen) including an input area in which various information can be input. In the input screen 100, information read using a code reader function is input to a predetermined input area, or information input by a user operation via the input device 13 is input. Note that the input area into which the information read using the code reader function is input may be specified by the input device 13. In addition, when an object including a code is captured by the camera 12, the display device 14 displays a preview screen 110 (an example of a first screen) including the captured image. Therefore, the user can make necessary inputs to the input screen 100 while checking the preview screen 110 displayed on the display device 14, that is, while checking the object.
[0026] The display device 14 is capable of displaying a plurality of screens including a preview screen 110 and an input screen 100. Conventionally, the preview screen 110 has been displayed overlapping the input screen 100 on which the user performs input, making it difficult to check the input screen 100 and making it difficult to input data on the input screen 100. Generally, the screen displayed on the top layer is the active screen, i.e., the screen on which input is valid, but when the preview screen 110 is placed on the top layer, it can be difficult to input data on the input screen 100 placed on the lower layer.
[0027] In contrast, in the code reader device 10 according to this embodiment, the processor 11 controls the superimposition state of the preview screen 101 and the input screen 100, so that the user can input data into the input area of the input screen 100 while checking the preview screen 110, even after the preview screen 101 is superimposed on the input screen 100. This allows the user to easily input data into the input area of the input screen 100 using a code (i.e., using the code reader function) while checking the preview screen 110.
[0028] The memory 15 includes a primary storage device (e.g., Random Access Memory (RAM) or Read Only Memory (ROM). The memory 15 may include a secondary storage device (e.g., a Hard Disk Drive (HDD) or a Solid State Drive (SSD)) or a tertiary storage device (e.g., an optical disk or an SD card). The memory 15 may be an external storage medium or may be detachable from the code reader device 10. The memory 15 stores various data, information, images (e.g., captured images), programs, etc. The memory 15 may also store various trained models.
[0029] The code reader device 10 can, for example, identify packages based on a code included in an image captured by a user, and store the identification results, thereby facilitating management of packages (sorting, shipping, etc.).
[0030] The code reader device 10 may include a communication device. The communication device communicates various data or information according to a wired or wireless communication method. The communication device may be communicatively connected to a network. The communication method used by the communication device may include a local area network (LAN), a wide area network (WAN), a mobile phone network, power line communication, short-range wireless communication (e.g., Bluetooth (registered trademark), NFC (registered trademark)), and other communication methods.
[0031] For example, an external server may perform at least a part of the processing by the processor 11, and necessary data may be communicated between the external server and the code reader device 10 via a communication device. Also, the code reader device 10 may not include the camera 12, and the communication device may receive captured images from a device that includes the camera 12 and send image capture instructions to the camera 12.
[0032] <Code reader operation> FIG. 6 is a diagram showing screen transitions on the display device 14 by the code reader device 10 and their explanations.
[0033] When the input device 13 receives a user operation, the processor 11 starts a predetermined application (for example, an application for package delivery) and displays an input screen 100 on the display device 14 (state 1).
[0034] The processor 11 activates the input area 102 of the input screen 100 displayed on the display device 14, that is, enables the input area 102 to a state where input is possible into the input area 102. This enables input by operating the input area 102 (e.g., the input field 102a or the input keys 102b) (state 2). In addition, the processor 11 designates a specific input area out of one or more input areas 102 into which information (e.g., the result of reading a code) is to be input. The specific input area is activated.
[0035] When the processor 11 detects that the read start instruction switch 13R of the input device 13 is turned on (e.g., pressed), it instructs the start of reading the code. Then, the processor 11 activates a code reader function and causes the camera 12 (e.g., rear camera 12B) to start capturing an image of a subject including a code. The processor 11 acquires an image captured by the camera 12, and causes the display device 14 to display a preview screen 110 including the captured image (state 3). The preview screen 110 is displayed, for example, by a pop-up screen. The preview screen 110 is displayed superimposed on the input screen 100. The user can check the status of the code, such as the position of the code relative to the camera 12, by checking the preview screen 110.
[0036] For example, the user can move the code reader device 10 and adjust the position and attitude of the camera 12 so that the code is included in the imaging range of the camera 12, thereby allowing the camera 12 to capture an image of a subject including a code. When the processor 11 acquires a captured image of a subject including a code by the camera 12 (State 4), the processor 11 acquires (e.g., extracts) the code from the captured image. The processor 11 reads the code by performing image processing on the acquired code.
[0037] If the code is successfully read, the processor 11 displays the code reading result (e.g., the code identification number) in a specified specific input area 102 (e.g., a specific input field 102a) of the input screen 100. Then, the processor 11 erases (i.e., makes hidden) the preview screen 110, and reflects the reading result in the specific input area 102 (e.g., a specific input field 102a) and displays it on the display device 14 (state 5). In this way, the processor 11 displays the preview screen 110 for the period from the activation of the code reader function until the code is successfully read. The processor 11 continues to display the preview screen 110 during the period during which the code is not successfully read.
[0038] If the code cannot be read, the processor 11 may input information corresponding to the code via the input key 102b in the specific input area 102. The input key 102b is also activated and operable.
[0039] The processor 11 may set any of the operation modes (for example, normal reading mode, continuous reading mode, semi-transparent mode, or other operation mode) via, for example, the input device 13. For example, when the continuous reading mode is set as the operation mode, the processor 11 can capture images continuously with the camera 12 when the code reader function is activated. In this case, the processor 11 may continuously display the preview screen 101. As will be described later, when the input screen 100 is difficult to see due to the preview screen 110, the preview screen 110 may be manually erased via the input device 13.
[0040] When processor 11 detects that read start instruction switch 13R has been turned off, processor 11 may erase the preview screen 110 that was being displayed. Even in this case, if the code has been successfully read, processor 11 may continue to display the read result in input area 102 (e.g., specific input field 102a). As will be described later, when moving or changing the size of code preview screen 110, processor 11 may not erase preview screen 110 even if read start instruction switch 13R is switched from on to off.
[0041] Next, the screen control by the code reader device 10 will be described in detail.
[0042] (First screen control example) Fig. 7 is a diagram showing a control flow by the code reader device 10 according to the first screen control example, and Fig. 8 is a diagram showing screen transitions by the code reader device 10 according to the first screen control example.
[0043] In the first screen control example, the operation mode is set to, for example, the normal reading mode or the continuous reading mode, and also to the movement mode.
[0044] When the input device 13 receives a user operation, the processor 11 starts a predetermined application (for example, an application for package delivery) and displays an input screen 100 on the display device 14 (step S1).
[0045] The processor 11 activates the input area 102 of the input screen 100 displayed on the display device 14, that is, enables input in the input area 102 (step S2). This enables input by operating the input area 102 (e.g., the input field 102a or the input key 102b) (state 2). For example, in FIG. 8, the processor 11 designates a specific input field 102a (e.g., the input field 102a for "3") among multiple input fields 102a (e.g., four input fields 102a for "1", "2", "3", and "4") via the input device 13 as a specific input area 102 for inputting the code reading result. Note that in FIG. 8, input has already been made into the input field 102a for "1" before input into the input field 102a for "3".
[0046] When processor 11 detects that read start instruction switch 13R of input device 13 is turned on (e.g., pressed), it instructs to start reading the code (step S3). Then, processor 11 activates the code reader function and causes camera 12 to start capturing an image of a subject including a code. Processor 11 acquires the captured image captured by camera 12, and causes display device 14 to display preview screen 110 including the captured image (step S4).
[0047] As shown in FIG. 8, the preview screen 110 is displayed superimposed on the input screen 100. Here, it is assumed that the user touches the preview screen 110 to perform a scroll operation. In this case, the processor 11 detects the touch of the user's finger or the like on the preview screen 110 via the input device 13 (step S5), and detects an input operation of scrolling the preview screen 110 with the finger (step S6). This allows the user to move the preview screen 110 to a position that does not overlap with a specific input area 102 (input field 102a (102a3) of "3" in FIG. 8) on the input screen 100. That is, the user can drag the preview screen 110 to display it while avoiding the specific input field 102a by performing an input operation using the input device 13. This makes it easier for the user to perform input using the code reader function while visually recognizing not only the preview screen 110 but also the specific input area 102. The above-mentioned movement of the preview screen 110 is an example of controlling the specific input area 102 to be visually recognizable.
[0048] In this way, based on an input operation on the input device 13, the processor 11 may move the preview screen 110 relative to the input screen 100 so as not to overlap a specific input area 102 on the input screen 100 (in this figure, the input field 102a for "3").
[0049] For example, the user can move the code reader device 10 and adjust the position and attitude of the camera 12 so that the code is included in the imaging range of the camera 12, thereby allowing the camera 12 to capture an image of a subject including a code. When the processor 11 obtains a captured image of a subject including a code by the camera 12, the processor 11 obtains (e.g., extracts) the code from the captured image (step S7). The processor 11 reads the code by performing image processing on the obtained code.
[0050] If the processor 11 successfully reads the code, it erases the preview screen 110 from the display screen (step S8), and displays the code reading result (e.g., the code identification number) in a specific input area 102 (e.g., input field 102a for "3") on the input screen 100 (step S9).
[0051] According to this screen control example, the preview screen 110 does not overlap a specific input area 102 (e.g., the input field 102a for "3") of the input screen 100, so that the user can visually confirm the specific input area 102. Furthermore, since the input area 102 of the input screen 100 is enabled, input into the specific input area 102 is possible even after the preview screen 110 is superimposed and arranged on the input screen 100. Therefore, the user can easily input into the input area 102 using a code while checking the preview screen 110. Therefore, the code reader device 10 moves the preview screen 110 in correspondence with the specific input area 102 into which the user wants to input the code reading result, and can suppress the preview screen 110 from interfering with the use of the application.
[0052] The processor 11 may automatically determine the display position of the preview screen 110 after the movement, instead of determining it via the input device 13. For example, information on the display position of the preview screen 110 after the movement may be stored in the memory 15 in association with a plurality of input fields 102a or input keys 102b as the input area 102. The processor 11 may move the preview screen 110 to a display position of the preview screen 110 after the movement associated with a specified specific input area 102 (e.g., the input field 102a of "3") by referring to the memory 15. Even in this case, the code reader device 10 can prevent the display of the preview screen 110 from overlapping with the specific input area 102 that is the input target, thereby facilitating input to the input area 102 using a code.
[0053] (Second screen control example) Fig. 9 is a diagram showing a control flow by the code reader device 10 according to the second screen control example. Fig. 10 is a diagram showing screen transitions by the code reader device 10 according to the second screen control example. In Fig. 9, the same processes as those in Fig. 7 are given the same reference numerals, and their explanations are omitted or simplified. The procedure from step S1 to step S5 in Fig. 9 is the same as in the first screen control example.
[0054] In the second screen control example, the operation mode is set to, for example, the normal reading mode or the continuous reading mode, and also to the movement mode.
[0055] As shown in FIG. 10, the preview screen 110 is displayed superimposed on the input screen 100. Here, it is assumed that the user touches the preview screen 110 to perform a pinch-in operation. In this case, the processor 11 detects the touch of the user's finger or the like on the preview screen 110 via the input device 13 (step S5), and detects an input operation of pinching the preview screen 110 with the finger (step S10). This allows the user to change the display size of the preview screen 110 to a position where it does not overlap with a specific input area 102 (input field 102a of "3" in FIG. 10) on the input screen 100. That is, the user can reduce the preview screen 110 and display it avoiding the specific input field 102a by performing an input operation using the input device 13. This makes it easier for the user to perform input using the code reader function while visually checking not only the preview screen 110 but also the specific input area 102. The reduction of the preview screen 110 described above is an example of controlling the specific input area 102 to be visually visible.
[0056] The procedure from step S7 to step S9 in FIG. 9 onwards is the same as that in the first screen control example.
[0057] In this way, the processor 11 may move the preview screen 110 relative to the input screen 100 so as not to overlap with a specific input area 102 (input field 102a of "3" in this figure) of the input screen 100 based on an input operation to the input device 13, and may reduce the preview screen 110 in this screen control example in particular. Note that the processor 11 may only reduce the preview screen 110 without moving it, depending on the positional relationship between the specified specific input area 102 and the display position of the preview screen 110.
[0058] According to this screen control example, the reduced preview screen 110 does not overlap with the specific input area 102 of the input screen 100, so the user can visually confirm the specific input area 102. Therefore, the user can easily input data into the specific input area 102 using a code while checking the reduced preview screen 110. Therefore, the code reader device 10 changes the display size of the preview screen 110 in accordance with the specific input area 102 into which the user wishes to input the results of reading the code, thereby suppressing interference with the use of an application caused by the preview screen 110.
[0059] The processor 11 may automatically determine the display size of the reduced preview screen 110 instead of determining it via the input device 13. For example, information on the display size of the reduced preview screen 110 may be stored in the memory 15 in association with a plurality of input fields 102a or input keys 102b as the input area 102. The processor 11 may change the display size of the preview screen 110 to the display size of the reduced preview screen 110 associated with a specified specific input area 102 (e.g., the input field 102a for "3") by referring to the memory 15. Even in this case, the code reader device 10 can prevent the display of the preview screen 110 from overlapping with the specific input area 102 that is the input target, thereby facilitating input into the input area 102 using a code.
[0060] (Third screen control example) Fig. 11 is a diagram showing a control flow by the code reader device 10 according to the third screen control example. Fig. 12 is a diagram showing screen transitions by the code reader device 10 according to the third screen control example. In Fig. 11, the same processes as those in Fig. 7 or Fig. 9 are given the same reference numerals, and their explanations are omitted or simplified. The procedure from step S1 to step S4 in Fig. 11 is the same as in the first screen control example.
[0061] In the third screen control example, the operation mode is set to, for example, the normal reading mode or the continuous reading mode, and also to the movement mode.
[0062] The third screen control example differs from the first and second screen control examples in that the preview screen 110 is not automatically erased after successful code reading, but is instead erased based on an explicit instruction from the user via the input device 13.
[0063] In this screen control example, after the preview screen 110 is displayed (step S4), for example, the user moves the code reader device 10 to adjust the position and attitude of the camera 12 so that the code is included in the imaging range of the camera 12, thereby enabling the camera 12 to capture an image of a subject including a code. When the processor 11 acquires a captured image of a subject including a code by the camera 12, the processor 11 acquires (e.g., extracts) the code from the captured image (step S7). The processor 11 reads the code by performing image processing on the acquired code.
[0064] At this time, as shown in FIG. 12, it is assumed that the user double taps the preview screen 110 with a finger. In this case, the processor 11 detects an input operation of a double tap with the user's finger or the like on the preview screen 110 via the input device 13 (step S11). In this case, the processor 11 erases the preview screen 110 from the display screen after a predetermined time has elapsed since the detection of the double tap (step S8). Therefore, after the user checks the preview screen 110 within the predetermined time, the user can operate the input field 102a (for example, the input field 102a for "4" here) while visually checking the input field 102a. The procedure of the subsequent step S9 is the same as that of the first screen control example.
[0065] In this way, the processor 11 erases the preview screen 110 after a predetermined time has elapsed based on an input operation to the input device 13.
[0066] According to this screen control example, the preview screen 110 is erased after a predetermined time has elapsed, so that the user can view the specific input area 102. Therefore, after the code reading is completed, the user can change the preview screen 110 to a hidden state in response to an explicit user instruction, thereby suppressing the preview screen 110 from interfering with the use of the application.
[0067] The processor 11 may erase the preview screen 110 after a predetermined time has elapsed based on an input operation to the input device 13 before the code is successfully read. In this case, the user can appropriately operate the code reader device 10 by checking the state of the captured image before the preview screen 110 is erased. In this case, like the first screen control example and the second screen control example, the code reader device 10 can prevent a specific input area 102 from being hidden by the preview screen 110, and the user can easily input into the input area 102 using the code.
[0068] (4th screen control example) 13A and 13B are diagrams showing a control flow by the code reader device 10 according to the fourth screen control example. FIG. 13A is a diagram showing a control flow by the code reader device 10 at a first timing, and FIG. 13B is a diagram showing a control flow by the code reader device 10 when performing screen control again at a second timing after the first timing. The time when performing screen control again includes, for example, when a specific application is restarted, when performing screen control when reading a plurality of codes in sequence, or when displaying a preview screen 110 a plurality of times when reading the same code. FIG. 14 is a diagram showing a screen transition by the code reader device 10 according to the fourth screen control example. In FIG. 13A and FIG. 13B, the same processes as those in FIG. 7, FIG. 9, or FIG. 11 are denoted by the same reference numerals, and the description thereof will be omitted or simplified.
[0069] In the fourth screen control example, the operation mode is set to, for example, the normal reading mode or the continuous reading mode, and also to the movement mode or the semi-transparent mode.
[0070] 13A are the same as those in the first screen control example. In this screen control example, processor 11 detects the position of preview screen 110 displayed in step S4, and stores position information relating to the position of preview screen 110 relative to the display screen of display device 14 in memory 15 (step S12).
[0071] After the process of Fig. 13A is completed, for example, when the code reader device 10 executes the application again at an arbitrary second timing after once terminating the application, the code reader device 10 executes the control flow of Fig. 13B. The procedure of steps S1 to S3 in Fig. 13B is the same as that of the first screen control example.
[0072] Next, processor 11 calls up from memory 15 the position information of preview screen 110 stored in step S12 of Fig. 13A (step S13). Processor 11 determines the position of preview screen 110 with respect to the display screen of display device 14 according to the called position information of preview screen 110, and displays the preview screen at this position (step S4). Thereafter, processor 11 executes steps S7 to S9 in the same manner as in the first screen control example. Processor 11 then again detects the position of preview screen 110 displayed in step S4, and stores the position information relating to the position of preview screen 110 in memory 15 (step S12).
[0073] In addition, in step S12, processor 11 may store not only the position information of preview screen 110 but also other information related to preview screen 110 (for example, information on the display size of preview screen 110), and in step S13, may call up the other information related to the preview screen and reflect it in the initial state of the display of the preview screen at the second timing.
[0074] 14, processor 11 stores information (e.g., information on the display position and display size) related to preview screen 110 on display screen G1 at a first timing in memory 15. At a second timing, processor 11 refers to the information related to the preview screen stored in memory 15, and displays preview screen 110 on display screen G2 at the second timing in accordance with this information.
[0075] Therefore, the code reader device 10 can display a later preview screen 110 at different timings by taking over the display state of a previous preview screen 110. Therefore, even if the preview screen 110 is erased from the display screen once, the preview screen 110 can be displayed in the same display state. Even if the application or the code reader device 10 is restarted, the display state of the preview screen 110 can be taken over and resumed in the same manner. Even if different input areas 102 are designated as the specific input area 102 at the first timing and the second timing, for example, the input field 102a for "1" is designated at the first timing and the input field 102a for "2" is designated at the second timing, the processor 11 can take over and display the display state of the preview screen 110.
[0076] In this way, processor 11 may store, in memory 15, position information regarding the position of preview screen 110 displayed at the first timing relative to input screen 100. When processor 11 issues an instruction to start reading a code after display of preview screen 110 at the first timing ends, processor 11 may display preview screen 110 relative to input screen 100 at the second timing based on the position information.
[0077] As a result, when the code is repeatedly read, for example, the previously suitable position of the preview screen can be stored and used as the initial position of the preview screen 110 the next time.
[0078] (Fifth screen control example) Fig. 15 is a diagram showing a control flow by the code reader device 10 according to the fifth screen control example. Fig. 16 is a diagram showing screen transitions by the code reader device 10 according to the fifth screen control example. Note that in Fig. 15, the same processes as those in Fig. 7, Fig. 9, Fig. 11, or Fig. 13 are given the same reference numerals, and their explanations are omitted or simplified.
[0079] In the fifth screen control example, the operation mode is set to, for example, the normal reading mode or the continuous reading mode, and is also set to the semi-transparent mode.
[0080] In this screen control example, first, processor 11 receives a user operation via input device 13, for example, and sets the operation mode of preview screen 110 to a semi-transparent mode (step S14). The semi-transparent mode is a mode in which preview screen 110 is displayed semi-transparently, thereby making a screen (for example, input screen 100) arranged below preview screen 110 visible. The procedures of steps S1 to S3 after step S14 in FIG. 15 are the same as those in the first screen control example.
[0081] When the processor 11 detects that the read start instruction switch 13R of the input device 13 is turned on (e.g., pressed), it instructs the start of reading the code (step S3). Then, the processor 11 activates the code reader function and causes the camera 12 to start capturing an image of a subject including a code. The processor 11 acquires the captured image captured by the camera 12, and causes the display device 14 to display a preview screen 110 including the captured image in a semi-transparent state (step S16). Therefore, the user can also view the screen of the input screen 100 in the area below the preview screen 110 (e.g., the input screen 100) through the preview screen 110. The subsequent procedures of steps S7 to S9 are the same as those of the first screen control example.
[0082] As shown in FIG. 16, the processor 11 displays the preview screen 110 in a semi-transparent state, superimposed on the input screen 100. Therefore, the user can see through the input screen 100 below the preview screen 110 without having to move the preview screen 110 so as not to overlap with the specific input area 102 of the input screen 100. For example, the user can input using a code while viewing the specific input area 102 (e.g., the input field 102a for "2") that is the input target. Note that the display of the preview screen 110 in a semi-transparent state is an example of controlling the specific input area 102 to be visible.
[0083] In this manner, the processor 11 displays the preview screen 110 in a semi-transparent state, superimposed on the input screen 100. Thus, by displaying the preview screen 110 in a semi-transparent state, even if the preview screen 110 is superimposed on the input screen 100, the user can view the input screen 100 without making the preview screen 110 smaller. Furthermore, since the input area 102 of the input screen 100 is enabled, input into a specific input area 102 is possible even after the preview screen 110 is superimposed on the input screen 100. Therefore, the user can easily perform input into the input area 102 using a code while checking the preview screen 110.
[0084] The code reader device 10 may execute a combination of at least two of the above-mentioned first to fifth screen control examples.
[0085] <Screen layout and input availability> Next, the layout of multiple screens and the effectiveness of input will be described.
[0086] Fig. 17 is a conceptual diagram showing a state of screen overlap in the code reader device 10. Fig. 18 is a diagram showing an example of a screen display by the code reader device 10. Note that the sixth screen control example is a control essential to the code reader device 10.
[0087] When the processor 11 displays the preview screen 110, the processor 11 displays the preview screen 110 in front (at a higher level) than the input screen 100. Even in this case, as shown in FIG. 17, the processor 11 sets the validity of the input so that the input screen 100, which is located below the preview screen 110, is higher than the preview screen 110. In other words, the processor 11 activates the input area 102 of the input screen 100 so that input is possible even if the preview screen 110 is located in front of the input screen 100. Therefore, the user can perform input using a code for a specified specific input area 102 in the input screen 100, even if the preview screen 110 is located at a higher level than the input screen 100.
[0088] In this way, the processor 11 may always display the preview screen 110 in the foreground. Even in this case, the input area 102 is activated, so the user can input data into the input area 102 while checking the preview screen 110.
[0089] In this way, according to the code reader device 10 of the present embodiment, the preview screen 110 is displayed so as not to overlap the specific input area 102, which is the input target of the input screen 100, or the preview screen 110 is displayed in a semi-transparent state. Therefore, the code reader device 10 allows the input screen 100 to be confirmed, and makes it easy to input data on the input screen 100. Furthermore, even if the preview screen 110 is arranged in the top layer, the code reader device 10 is in an active state in which input data can be input to the input area 102 of the input screen 100 arranged in the lower layer, so that input data can be input to the specific input area 102. Therefore, input data using a code can be easily performed in the input area 102 while displaying the preview screen 110 which is an image of the code.
[0090] In the above embodiment, the reading start instruction switch 13R is physically provided by hardware, but the present invention is not limited to this. The reading start instruction switch 13R may be functionally provided by a software switch on the touch panel 13A.
[0091] In the above embodiment, the code reading result is input and displayed in the specific input area 102, but this is not limited to the above. The processor 11 may input any information to the specific input area 102 via the input device 13, for example.
[0092] (Overview of the embodiment) As a result, the present disclosure includes at least the following items. Note that in parentheses, examples of components corresponding to the above-described embodiment are given, but the present disclosure is not limited to these.
[0093] (Item 1) A screen control device (code reader device 10) that controls multiple screens, A camera (camera 12) for capturing an image of a subject; A display device (display device 14) for displaying the plurality of screens; A processor (processor 11) that controls the plurality of screens, The plurality of screens include: A first screen (preview screen 110) including an image captured by the camera; a second screen (input screen 100) including an input area (input area 102) into which information can be input; The processor, Activating the input area of the second screen to enable input to the input area; Specifying a first input area (a specific input area) into which the information is to be input, among the one or more input areas; controlling the first input area of the second screen to be visible, and displaying the first screen on the display device in a superimposed manner in front of the second screen; Screen control device.
[0094] As a result, the screen control device enables the input area of the second screen and displays the first screen in front of the second screen in a state in which the first input area of the second screen is visible, allowing the user to easily input information into the input area while checking the first screen.
[0095] (Item 2) the first input area is an input area for inputting a code reading result as the information, The processor, Instruct the code reading to begin; In response to an instruction to start reading the code, the camera is caused to capture an image of a subject including the code, and the first screen is displayed in front of the second screen in a superimposed manner. A screen control device according to item 1.
[0096] This allows the user to easily input the result of code reading into the input area using the code while checking the first screen.
[0097] (Item 3) When controlling the first input area of the second screen to be visible, the processor moves the first screen relative to the second screen so as not to overlap the first input area of the second screen. A screen control device according to item 1 or 2.
[0098] As a result, the screen control device does not overlap the first input area of the second screen with the first screen, so that the user can easily input information into the input area while viewing the first input area.
[0099] (Item 4) An input device that accepts an input operation, the processor moves the first screen relative to the second screen so as not to overlap the first input area of the second screen based on the input operation to the input device; A screen control device according to item 3.
[0100] Thereby, the screen control device can move the first screen relative to the second screen to a position intended by the user based on a user operation so as not to overlap with the first input area of the second screen.
[0101] (Item 5) When controlling the first input area of the second screen to be visible, the processor causes the first screen to be superimposed on the second screen in a semi-transparent state. A screen control device according to item 1 or 2.
[0102] As a result, by the screen control device displaying the first screen in a semi-transparent state, even if the first screen is displayed superimposed on the first input area of the second screen, the user can easily input information into the input area while viewing the first input area without having to move the first screen, etc.
[0103] (Item 6) The processor, retaining position information regarding a position of the first screen displayed at a first timing relative to the second screen; when an instruction to start reading the code is given after the display of the first screen at the first timing is completed, the first screen is displayed on the second screen at a second timing based on the position information. A screen control device according to item 2.
[0104] As a result, when the screen control device repeatedly reads the code, for example, it can store the previously suitable position of the preview screen and use it as the initial position of the preview screen for the next time.
[0105] (Item 7) A screen control device described in any one of items 1 to 6, wherein when the processor controls the first input area of the second screen to be visible, the processor reduces the first screen so that it does not overlap with the first input area of the second screen.
[0106] As a result, the reduced first screen does not overlap with the first input area of the first screen, so that the user can easily input information into the input area while viewing the first input area.
[0107] (Item 8) A screen control method for controlling a plurality of screens, comprising: The plurality of screens include: a first screen including an image captured by a camera; a second screen including an input area into which information can be input; The screen control method includes: enabling the input area of the second screen to allow input to the input area; designating a first input area, among the one or more input areas, into which the information is to be input; controlling the first input area of the second screen to be visible, and displaying the first screen on a display device in a superimposed manner in front of the second screen; A screen control method comprising:
[0108] This will achieve the same effect as item 1.
[0109] Although various embodiments have been described above with reference to the drawings, it goes without saying that the present disclosure is not limited to such examples. It is clear that a person skilled in the art can come up with various modified or amended examples within the scope of the claims, and it is understood that these also naturally belong to the technical scope of the present disclosure. In addition, the components in the above embodiments may be arbitrarily combined within the scope of the invention.
[0110] In addition, the above embodiment may also be applicable to a program that realizes the functions of the screen control method, which is supplied to a computer (e.g., the code reader device 10) via a network or various storage media, and which is read and executed by the processor of the computer, as well as to a storage medium on which the program is stored.
[0111] Furthermore, the order of execution of each process, such as operations, procedures, steps, and stages, in the devices, systems, programs, and methods shown in the claims, specifications, and drawings is not specifically stated as "before," "prior to," etc., and can be realized in any order unless the output of a previous process is used in a later process. Even if the operational flow in the claims, specifications, and drawings is explained using "first," "next," etc. for convenience, it does not mean that it is essential to perform the process in this order. [Industrial Applicability]
[0112] The present disclosure is useful for a screen control device, a screen control method, and the like that can easily input information into an input area while displaying a preview screen including a captured image. [Explanation of symbols]
[0113] 10 Code reader device 11 Processors 12 Camera 13 Input Devices 13A Touch Panel 13B, 13C, 13D Function Switch 13R Read start switch 14 Display Devices 15 Memory 100 Input screen 102 Input Area 102a Input field 102b Input key 110 Preview Screen
Claims
1. A camera for capturing an image of a subject including a code, a display device, and a processor, The processor, When you launch a specific application, Displaying an input screen on the display device; Activating the input screen to enable input to an input area of the input screen while displaying a preview screen in which the subject is captured, on the display device, in front of the input screen; The preview screen is kept displayed in front of the input screen until the code is successfully read. Mobile device.
2. The processor, If the code is successfully read, a result of the code being read is displayed in the input area of the input screen. The mobile terminal according to claim 1.
3. The processor, If the code is successfully read, the display of the preview screen is erased.
3. The mobile terminal according to claim 1 or 2.
Citation Information
Patent Citations
Rejected character display system of OCR
JP1986131082A
Registration device and program
JP2023092870A
Preview screen control method
JP2008293148A