Enhanced multi-monitor layout

Abstract

A method includes receiving display data for a plurality of displays by using a processor, the display data for each display including a physical size, a display resolution, a display position, and a scale factor; receiving transition preferences; and calculating display transitions between adjacent displays based on the display data and the transition preferences. The transition preferences specify one of a physical parameter preference and a logical parameter preference for each display-to-display boundary of the plurality of displays. The method enhances a multi-display arrangement to provide a smooth, consistent display viewing experience for a user.

Description

Technical Field

[0001] The present disclosure relates to display arrangements and more particularly to enhancing multi-display arrangements. Background Art

[0002] Computer users often use multiple monitors. The transition effect of monitor boundaries needs to be enhanced. Summary of the invention

[0003] The present disclosure provides a method for enhancing a multi-display arrangement. The method includes receiving display data of a plurality of displays. The display data of each display includes a physical size, a display resolution, a display position, and a scale factor. The method also includes receiving a transition preference that specifies one of a physical parameter preference and a logical parameter preference for each display of the plurality of displays to a display boundary; and calculating a display transition between adjacent display viewers based on the display data and the transition preference.

[0004] In some embodiments the method further comprises presenting information on each of the plurality of displays using a physical scale and a logical scale of each display.

[0005] In some embodiments, calculating the display transition includes calculating pixel positions and rendering pixel sizes of adjacent pixels based on a display resolution, a logical scale, a physical scale, an edge size, and a pixel size of the adjacent display.

[0006] In some embodiments, the display transition comprises aligning the display to a display boundary.

[0007] In some embodiments, the display transition includes scaling the adjacent displays to present equivalent rendered pixel sizes.

[0008] In some embodiments, the display transitioning includes providing a smooth transition across the display to display boundary.

[0009] In some embodiments the method further comprises, in response to a linear pointer movement from the first display to the second display across the display-to-display boundary, placing a cursor on a linear vector corresponding to the linear pointer movement.

[0010] In some embodiments, the logical ratio is used to determine the rendering pixel size for each display.

[0011] In some embodiments, the rendered pixel size for each display adjacent to a given display-to-display boundary is equal.

[0012] The present disclosure provides an apparatus. The apparatus includes a processor and a memory storing code. The code can be executed by the processor to receive display data of multiple displays, receive transition preferences, and calculate display transitions between adjacent displays based on the display data and the transition preferences. The display data of each display includes physical size, display resolution, display position, and scale factor. The transition preference specifies one of a physical parameter preference and a logical parameter preference for each display-to-display boundary of the multiple displays.

[0013] In some embodiments, the code is further executable by the processor to present information on each of the plurality of displays using a physical scale and a logical scale of each display.

[0014] In some embodiments, the code is further executable by the processor to calculate pixel positions and rendering pixel sizes of neighboring pixels based on a display resolution, a logical scale, a physical scale, an edge size, and a pixel size of the neighboring display.

[0015] In some embodiments, the display transition comprises aligning the display to a display boundary.

[0016] In some embodiments, the display transition includes scaling the adjacent displays to present equivalent rendered pixel sizes.

[0017] In some embodiments, the display transitioning includes providing a smooth transition across the display to display boundary.

[0018] In some embodiments, the code is further executable by the processor to, in response to a linear pointer movement from a first display to a second display across the display-to-display boundary, place a cursor on a linear vector corresponding to the linear pointer movement.

[0019] In some embodiments, the logical ratio is used to determine the rendering pixel size for each display.

[0020] In some embodiments, the rendered pixel size for each display adjacent to a given display-to-display boundary is equal.

[0021] The present disclosure discloses a computer-readable storage medium storing processor executable code. The code is executed to receive display data of a plurality of displays, receive transition preferences, and calculate display transitions between adjacent displays based on the display data and the transition preferences. The display data of each display includes a physical size, a display resolution, a display position, and a scale factor. The transition preferences specify one of a physical parameter preference and a logical parameter preference for each display-to-display boundary of the plurality of displays.

[0022] In some embodiments, the code is further executable by the processor to present information on each of the plurality of displays using a physical scale and a logical scale of each display.

[0023] In an embodiment of the present disclosure, the display data and the transition preference of each display in the plurality of displays are received, and the display transition between adjacent displays is calculated. The display transition includes aligning the display to the display boundary and / or scaling adjacent displays to provide a smooth, consistent display viewing experience. Therefore, the functionality of the computer and the display is enhanced. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] A more specific description of the embodiments briefly described above will be presented by reference to the specific embodiments shown in the accompanying drawings. It should be understood that these drawings only depict some embodiments and therefore should not be considered as limiting the scope of the present disclosure. The embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings.

[0025] Figure 1A is a schematic block diagram of multiple monitors provided by an embodiment of the present disclosure.

[0026] Figure 1B is a schematic diagram of multiple displays provided by an embodiment of the present disclosure.

[0027] Figure 2A It is a schematic block diagram of a display database provided by an embodiment of the present disclosure.

[0028] Figure 2B It is a schematic block diagram of transition data provided by an embodiment of the present disclosure.

[0029] Figure 2C It is a schematic block diagram of display data provided by an embodiment of the present disclosure.

[0030] Figure 2D It is a schematic block diagram of transition preference provided by an embodiment of the present disclosure.

[0031] Figure 2E It is a schematic block diagram of display transition provided by an embodiment of the present disclosure.

[0032] Figure 3 is a schematic diagram of multiple displays provided by an embodiment of the present disclosure.

[0033] Figure 4 It is a schematic block diagram of a computer provided by an embodiment of the present disclosure.

[0034] Figure 5 It is a schematic flow chart of the display enhancement method provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as systems, methods or program products. Therefore, the embodiments may take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects. These embodiments may all be collectively referred to herein as "circuit", "module" or "system". In addition, the embodiments may take the form of a program product. The program product is embodied in one or more computer-readable storage devices. The computer-readable storage device stores machine-readable code, computer-readable code and / or program code, hereinafter referred to as code. The storage device may be tangible, non-temporary and / or non-transmitting. The storage device may not contain signals. In a certain embodiment, the storage device uses only signals for accessing the code.

[0036] Many of the functional units described in this specification have been labeled as modules in order to more particularly emphasize their implementation independence. For example, a module can be implemented as a hardware circuit, including a custom large-scale integration (VLSI) circuit or gate array, an off-the-shelf semiconductor such as a logic chip, a transistor, or other discrete components. A module can also be implemented in a programmable hardware device, such as a field programmable gate array, a programmable array logic, a programmable logic device, etc.

[0037] Modules can also be implemented in code and / or software for various types of processors to perform. The identified code module can for example include one or more physical or logical blocks of executable code, which can for example be organized as objects, processes or functions. However, the executable files of the identified modules do not need to be physically placed together, but can include different instructions stored in different locations. When these instructions are combined together logically, the module is constituted and the described purpose of the module is realized.

[0038] In practice, a code module may be a single instruction or multiple instructions, and may even be distributed over several different code segments, between different programs, and across multiple memory devices. Similarly, operational data may be identified and described within a module, and may be embodied in any suitable form and organized in any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed in different locations, including on different computer-readable storage devices. When a module or portion of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0039] Any combination of one or more computer readable media may be used. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, device or apparatus, or any suitable combination of the foregoing.

[0040] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection with one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0041] The code for performing the operations of the embodiments may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, R, Java, Java Script, Smalltalk, C++, CSharp, Lisp, Clojure, PHP, etc., as well as conventional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code may be executed entirely on the user's computer, partially on the user's computer as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0042] The present embodiment can transmit data between electronic devices. The present embodiment can also transition data from a first format to a second format, including transitioning data from a non-standard format to a standard format and / or transitioning data from a standard format to a non-standard format. The present embodiment can modify, update and / or process data. The present embodiment can store received, transitioned, modified, updated and / or processed data. The present embodiment can provide remote access to data including updated data. The present embodiment can make data and / or updated data available in real time. The present embodiment can generate and send messages based on data and / or updated data in real time. The present embodiment can safely transmit encrypted data. The present embodiment can organize data for effective verification. In addition, the present embodiment can verify data in response to actions and / or lack of actions.

[0043] References to "one embodiment", "embodiment" or similar language throughout the specification mean that the specific features, structures or characteristics described in conjunction with the embodiment are included in at least one embodiment. Therefore, the phrases "in one embodiment", "in an embodiment" and similar language that appear throughout the specification may but do not necessarily refer to the same embodiment, but rather represent "one or more but not all embodiments", unless otherwise expressly specified. Unless otherwise expressly specified, the terms "include", "comprise", "have" and their variants represent "including but not limited to". Unless otherwise expressly specified, the enumerated list of items does not mean that any or all items are mutually exclusive. Unless otherwise expressly specified, the terms "one" and "the" also refer to "one or more". The term "and / or" represents an embodiment of one or more listed elements, wherein "A and / or B" represents an embodiment of a single element A, a single element B or elements A and B together.

[0044] In addition, the features, structures or characteristics described in the embodiments may be combined in any suitable manner. In the following description, many specific details are provided, such as programming examples, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments may be practiced without one or more specific details, or with other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid blurring aspects of the embodiments.

[0045] Aspects of the embodiments are described below with reference to schematic flow charts and / or schematic block diagrams of methods, devices, systems, and program products according to the embodiments. It should be understood that each box in the flow chart and / or schematic block diagram, as well as the combination of each box in the flow chart and / or schematic block diagram, can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to generate a machine, so that instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions / actions specified in the schematic flow chart and / or schematic block diagram blocks.

[0046] The code may also be stored in a storage device. The storage device may instruct a computer, other programmable data processing device or other device to operate in a specific manner so that the instructions stored in the storage device produce production elements including instructions for executing the functions / actions specified in the schematic flowchart and / or schematic block diagram blocks.

[0047] The code may also be loaded onto a computer, other programmable data processing device, or other device to cause a series of operational steps to be executed on the computer, other programmable device, or other device to create a computer-implemented process. The code executed on the computer or other programmable device provides a process for implementing the functions / actions specified in the flowchart and / or block diagram block or blocks.

[0048] The schematic flow charts and / or schematic block diagrams in the accompanying drawings illustrate possible implementation architectures, functions, and operations of devices, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flow charts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a code of a specified logical function.

[0049] It should also be noted that in some alternative implementations, the functions annotated in the blocks may not appear in the order annotated in the figure. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods that are equivalent in function, logic or effect to one or more blocks or portions thereof of the illustrated figures may be contemplated.

[0050] Although various arrow types and line types may be used in flow charts and / or block diagrams, they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiments. For example, arrows may indicate a waiting or monitoring period of unspecified duration between the enumerated steps of the depicted embodiments. It will also be noted that each block of the block diagram and / or flow chart, as well as the combination of blocks in the block diagram and / or flow chart, may be implemented by a hardware-based dedicated system or a combination of dedicated hardware and code that performs a specified function or action.

[0051] The description of the elements in each figure may refer to the elements of the previous figure. In all figures, the same numerals refer to the same elements, including alternative embodiments of the same elements.

[0052] Figure 1A 1 is a schematic block diagram of multiple monitors 100 provided by an embodiment of the present disclosure. In the depicted embodiment, a computer 105 displays information through multiple monitors 110. The information displayed by the monitors 110 should be coordinated between the monitors 110 to increase usability.

[0053] Figure 1B This is an example of the present disclosure Figure 1A Schematic diagram of multiple displays 110. In the depicted embodiment, the displays 110 have different sizes and relative positions. For example, adjacent pixels 120a-c of the displays 110a-c can have different sizes for each display. The first display 110a has adjacent pixel 120a at the lower right corner, the second display 110b has adjacent pixel 120b at the upper right corner, and the third display 110c has adjacent pixel 120c at the upper left corner. In addition, the physical size of each display 110 is different. The displays 110 are adjacent to both vertical and horizontal boundaries.

[0054] In the past, determining the display transitions between the adjacent displays 110 was primarily a manual process that relied on trial and error. Embodiments calculate the display transitions between the adjacent displays 110 to efficiently and effectively configure the displays 110 to display information, as will be described below.

[0055] Figure 2A 2 is a schematic block diagram of a display database 200 provided in an embodiment of the present disclosure. The display database 200 may store display data 201 for each of a plurality of displays 110. The display database 200 may be organized as a data structure in a memory. The display database 200 includes the display data 201 for each display 110. Figure 2C The display data 201 is described in.

[0056] Figure 2B 2 is a schematic block diagram of the transition data 220 provided by the embodiment of the present disclosure. The transition data 220 stores a transition preference 221 and a display transition 225 for each of the plurality of displays 110.

[0057] The transition preference 221 may specify one of a physical parameter preference and a logical parameter preference for each display-to-display boundary of the plurality of displays 110. In one embodiment, if the physical parameter preference is specified, the display 110 may display information primarily and / or solely based on a physical scale. Additionally, if the logical parameter preference is specified, the display 110 may display information primarily and / or exclusively based on a logical scale.

[0058] The display transition 225 specifies the pixel position and / or rendering pixel size of the adjacent pixel 120 based on the display resolution, logical scale, physical scale, edge size and / or pixel size of the adjacent display 110 , which will be described below.

[0059] Figure 2C 1 is a schematic block diagram of display data 201 provided by an embodiment of the present disclosure. The display data 201 may store data for a given display 110. The display data 201 may be organized as a data structure in a memory. In the depicted embodiment, the display data 201 includes a display identifier 203, a display resolution 205, a display orientation 207, an edge size 209, a neighbor identifier 211, a display position 221, a display-to-display boundary 213, a physical size 215, a scale factor 219, a physical scale 231, a logical scale 233, a rendering pixel size 223, a pixel position 227, and a pixel size 229.

[0060] The display identifier 203 may uniquely identify the display 110. The display resolution 205 may specify a resolution such as 1920 x 1080. The display orientation 207 may specify whether the display 110 is oriented in landscape, portrait, or at a specified angle.

[0061] The edge dimension 209 may specify the length of adjacent pixels of the adjacent display 110. The edge dimension 209 may be measured in physical dimensions and / or number of pixels.

[0062] The neighbor identifier 211 can record the display identifier 203 of the one or more adjacent displays 110 as an upper neighbor identifier 211a, a lower neighbor identifier 211b, a left neighbor identifier 211c and a right neighbor identifier 211d above the display 110, below the display 110, to the left of the display 110 and / or to the right of the display 110, respectively.

[0063] The display position 221 may specify a physical position of the display 110 in space. The display position 221 may be relative to the specified display 110. The display-to-display boundary 213 may specify an edge of the display 110 adjacent to another display 110. The physical size 215 may specify a physical length, a physical width, and / or a physical diagonal of the display 110.

[0064] The scale factor 219 may specify a proportional increase or decrease in the rendered pixel size 223. The physical scale 231 may specify a proportional increase or decrease in the rendered pixel size 223 based on the physical size 215. The logical scale 233 may specify a proportional increase in the rendered pixel size 223 based on the display resolution 205.

[0065] The pixel position 227 may specify the position of the neighboring pixel 120. The pixel size 229 may store the original pixel size of the display 110.

[0066] Figure 2D 2 is a schematic block diagram of a transition preference 221 provided by an embodiment of the present disclosure. The transition preference 221 may be organized as a data structure in a memory. In the depicted embodiment, the transition preference 221 includes the physical parameter preference 271 and the logical parameter preference 273. The physical parameter preference 271 and the logical parameter preference 273 may be received from a user and / or specified by user preference.

[0067] Figure 2E A schematic block diagram of a display transition 225 provided in an embodiment of the present disclosure. The display transition 225 is used to configure each display in the display 110. The display transition 225 can be organized as a data structure in a memory. In the depicted embodiment, the display transition 225 includes the pixel position 227, the rendering pixel size 223, the physical scale 231, the logical scale 233, the edge size 209, and the pixel size 229.

[0068] Figure 3 2 is a schematic diagram of a plurality of displays 110 provided by an embodiment of the present disclosure. In the depicted embodiment, the plurality of displays 110 are displayed at the display position 221 together with the corresponding display-to-display boundary 213. The display transition 225 may include aligning the display-to-display boundary 213. In addition, the display transition 225 may scale the adjacent displays 110 to display the equivalent rendered pixel size 223.

[0069] A transition 309 is shown between a first display 110a and an adjacent second display 110b. The display transition 225 can scale the adjacent first display 110a and the second display 110b to provide a smooth transition 309 across the display to display boundary 213. As used herein, the smooth transition 309 refers to adjacent pixels along the transition 309, where a first pixel on the first display 110a and a second pixel on the second display 110b function as adjacent pixels on a single physical display 110.

[0070] In one embodiment, the linear pointer movement of the cursor 305 between adjacent displays 110 places the cursor 305 on a linear vector 303 corresponding to the linear pointer movement. The linear pointer movement may be the movement of a mouse, trackball, stylus, or the like.

[0071] Figure 4 4 is a schematic block diagram of a computer 105 provided in an embodiment of the present disclosure. In the depicted embodiment, the computer 105 includes a processor 405, a memory 410, and communication hardware 415. The memory 410 can store code and data. The processor 405 can execute the code and process data. The communication hardware 415 can communicate with other devices such as the display 110.

[0072] Figure 5 is a schematic flow chart of a display enhancement method 500 provided by an embodiment of the present disclosure. The method 500 may calculate the display transition 225 between the one or more adjacent displays 110 and display information on the display 110. The method 500 may be executed by the computer 105 and / or the processor 405.

[0073] In one embodiment, the method 500 begins, at 501, the processor 405 receives the display data 201 of the plurality of displays 110. In one embodiment, the display data 201 includes at least the physical size 215, the display resolution 205, the display position 221, and the scale factor 219.

[0074] At 503, the processor 405 may receive the transition preference 221 for each display-to-display boundary 213. In one embodiment, the processor 405 presents at least one of the display-to-display boundary 213 to the user and receives 503 the corresponding transition preference 221. The transition preference 221 may specify one of the physical parameter preference 271 and the logical parameter preference 273 for the display-to-display boundary 213.

[0075] At 505, the processor 405 may calculate the display transition 225 between adjacent displays 110 based on the display data 201 and the transition preference 221. In one embodiment, the processor 405 calculates the physical scale 231 and / or the logical scale 233 for each display 110 of the plurality of displays 110. In addition, the processor 405 may calculate the pixel position 227 and the rendered pixel size 223 of the adjacent pixel 120 for the adjacent computer 110 based on the display resolution 205, the logical scale 233, the physical scale 231, the edge size 209, and the pixel size 209. In one embodiment, the logical scale 233 determines the rendered pixel size 223 of each display 110. The rendered pixel size 223 of each display 110 adjacent to a given display-to-display boundary 213 may be equal.

[0076] In one embodiment, if the transition preference 221 is the physical parameter preference 271, the display transition 225 adopts the physical scale 231. The physical scale 231 may specify a proportional increase or decrease in the rendering pixel size 223 based on the physical size 215.

[0077] In one embodiment, if the transition preference 221 is the logical parameter preference 273, the display transition 225 uses the logical scale 233. The logical scale 233 may specify a proportional increase in the rendering pixel size 223 based on the display resolution 205.

[0078] The display transition 225 may include aligning the display-to-display boundary 213. In addition, the display transition 225 may scale the adjacent displays 110 to present equivalent rendered pixel sizes 223. For example, the rendered pixel size 223 of the first display 110a may appear the same as the rendered pixel size 223 of the second adjacent display 110b even though the pixel sizes 229 of the first display 110a and the second display 110b are different.

[0079] The display transition 225 may include providing the smooth transition 309 across each display-to-display boundary 213. Figure 3 As shown, the linear pointer movement from the first display 110a to the second display 110b across the display-to-display boundary 213 places the cursor 305 on the linear vector 303 corresponding to the linear pointer movement. The pixel position 227 may provide the smooth transition 309.

[0080] At 507, the computer 105 and / or the processor 405 may present information on each of the plurality of displays 110, and the method 500 ends. The computer 105 and / or the processor 405 may present the information about each of the plurality of displays 110 at 507 using the physical dimensions 231 and / or the logical dimensions 233 of each display 110. In addition, the computer 105 and / or the processor 405 may present the information on each of the plurality of displays 110 based on the display transition 225.

[0081] The embodiment receives the display data 201 and the transition preferences 221 for each of the plurality of displays 110 and calculates the display transition 225 between adjacent displays 110. The display transition 225 includes aligning the display-to-display boundary 213 and / or scaling adjacent displays 110 to provide a smooth, consistent display viewing experience. Thus, the functionality of the computer 105 and the display 110 is enhanced.

[0082] The embodiments described may be practiced in other specific forms. The described embodiments are considered to be illustrative and not restrictive in all respects. Therefore, the scope of the present invention is indicated by the appended claims rather than by the foregoing description. All changes within the equivalent meaning and scope of the claims should be included within their scope.

Claims

1. A method for enhancing a display, comprising: receiving, using a processor, display data for a plurality of displays, the display data for each display comprising a physical size, a display resolution, a display position, and a scale factor; receiving transition preferences that specify one of a physical parameter preference and a logical parameter preference for each display-to-display boundary of the plurality of displays; as well as A display transition between adjacent displays is calculated based on the display data and the transition preference, wherein calculating the display transition includes calculating pixel positions and rendering pixel sizes of adjacent pixels in the adjacent displays based on display resolutions, logical scales and / or physical scales, edge sizes and pixel sizes of the adjacent displays.

2. The method according to claim 1, characterized in that Also included is presenting information on each of the plurality of displays using the physical scale and / or the logical scale of each display.

3. The method according to claim 1, characterized in that The display transition includes aligning the display to a display boundary.

4. The method according to claim 1, characterized in that The display transition includes scaling the adjacent displays to present equivalent rendering pixel sizes.

5. The method according to claim 1, characterized in that The display transitioning includes providing a smooth transition across the display to display boundary.

6. The method according to claim 1, characterized in that Also includes: In response to linear pointer movement from a first display to a second display across the display-to-display boundary, a cursor is placed on a linear vector corresponding to the linear pointer movement.

7. The method according to claim 1, characterized in that The logical scale is used to determine the rendering pixel size for each display.

8. The method according to claim 7, characterized in that The rendered pixel size for each display adjacent to a given display-to-display boundary is equal.

9. An apparatus for enhancing a display, comprising: processor; a memory storing code executable by the processor to: receiving display data for a plurality of displays, the display data for each display comprising a physical size, a display resolution, a display position, and a scale factor; receiving transition preferences that specify one of a physical parameter preference and a logical parameter preference for each display-to-display boundary of the plurality of displays; and A display transition between adjacent displays is calculated based on the display data and the transition preference, wherein calculating the display transition includes calculating pixel positions and rendering pixel sizes of adjacent pixels in the adjacent displays based on display resolutions, logical scales and / or physical scales, edge sizes and pixel sizes of the adjacent displays.

10. The device according to claim 9, characterized in that The code is further executable by the processor to present information on each of the plurality of displays using the physical scale and / or the logical scale of each display.

11. The device according to claim 9, characterized in that The display transition includes aligning the display to a display boundary.

12. The device according to claim 9, characterized in that The display transition includes scaling the adjacent displays to present equivalent rendering pixel sizes.

13. The device according to claim 9, characterized in that The display transitioning includes providing a smooth transition across the display to display boundary.

14. The device according to claim 9, characterized in that The code is further executable by the processor to, in response to a linear pointer movement from a first display to a second display across the display-to-display boundary, place a cursor on a linear vector corresponding to the linear pointer movement.

15. The device according to claim 9, characterized in that The logical scale is used to determine the rendering pixel size for each display.

16. The device according to claim 15, characterized in that The rendered pixel size for each display adjacent to a given display-to-display boundary is equal.

17. A computer readable storage medium storing processor executable code, the code being executed to: receiving display data for a plurality of displays, the display data for each display comprising a physical size, a display resolution, a display position, and a scale factor; receiving transition preferences that specify one of a physical parameter preference and a logical parameter preference for each display-to-display boundary of the plurality of displays; and A display transition between adjacent displays is calculated based on the display data and the transition preference, wherein: Calculating the display transition includes calculating pixel positions and rendered pixel sizes of adjacent pixels in the adjacent display based on display resolution, logical scale and / or physical scale, edge size, and pixel size of the adjacent display.

18. The computer-readable storage medium of claim 17, wherein: The code is further executable by the processor to present information on each of the plurality of displays using the physical scale and / or the logical scale of each display.

Images