Click here to Skip to main content
15,887,214 members
Home / Discussions / .NET (Core and Framework)
   

.NET (Core and Framework)

 
Question[Solved] Message Queue, sending a class including a bitmap Pin
bas-man823-Jul-13 0:06
bas-man823-Jul-13 0:06 
AnswerRe: Message Queue, sending a class including a bitmap Pin
bas-man823-Jul-13 22:50
bas-man823-Jul-13 22:50 
QuestionMessage Queue Pin
Member 997471330-Jun-13 1:06
Member 997471330-Jun-13 1:06 
AnswerRe: Message Queue Pin
Pete O'Hanlon30-Jun-13 10:57
mvePete O'Hanlon30-Jun-13 10:57 
GeneralRe: Message Queue Pin
Member 997471330-Jun-13 23:19
Member 997471330-Jun-13 23:19 
GeneralRe: Message Queue Pin
Pete O'Hanlon1-Jul-13 3:01
mvePete O'Hanlon1-Jul-13 3:01 
QuestionCan not move controls over a user control Pin
dSolariuM29-Jun-13 9:53
dSolariuM29-Jun-13 9:53 
QuestionDiscussion on Screen Size and MDI Pin
Ron Beyer26-Jun-13 12:20
professionalRon Beyer26-Jun-13 12:20 
I wanted to have a spirited discussion on a valid use case for screen size dependent forms design. I'd like to make it clear though, I'd love an alternative that fits my use case and is size independent.

So, here it goes:

Use Case
I develop applications for use in industrial control systems. The point of these screens is to place as much relevant information on a single display as possible while not overcrowding the display. This often includes piping diagrams, large gauges (as to be read from a distance or at a glance). The screen sizes are usually fixed at around 21" or 23" (widescreen is just breaking in) and are touch screen only (no keyboards).

Case for Big Screens
I really would love to discuss with developers who make blanket statements about big screens mean you are doing something wrong.

Here is an example screen

The above screen is a sample, the requirement is to show everything related to the pits on one screen so that while the operator is doing a particular operation they do not have to switch screens to see any of the data. The screen is actually from an HMI designer that I use (and designed) that uses Windows Forms as the back-end.

Now, knowing that we have:
1: A fixed screen size.
2: A product that we control what it runs on (we also provide the screens/computers)
3: Requirement from the user about what is shown.
4: Winforms back-end.
5: The designer does not have access to the code (HMI designers are NOT programmers, so they are not given or expected to write code, they just place stuff on the display and tie it to external devices through a binding interface).

How could we make this size independent? This is why, at least for me, Windows Forms limitation of 12px over the designer screen resolution is a PITA. Our field engineers making changes to screens typically use laptops to edit screens that run on 23" monitors, so every time they open a screen, WF graciously resizes them (thanks MS!).

Use for MDI
Aside from the system running full screen (we don't want the user to be able to access the desktop), we use an MDI window in the background to make sure that all the screens stay on the display they are assigned to. The application can be assigned to run on a certain display and we don't want the user to change that. So we use MDI as the container for the windows so that even if the form has a title bar, the user cannot drag them outside of the screen.

If somebody has a really cool way of doing what I need I'm all ears, but I think we should all stop assuming that because somebody says they need the screen bigger that they are doing it wrong fundamentally, since we don't fully understand the use case...
AnswerRe: Discussion on Screen Size and MDI Pin
Sergey Alexandrovich Kryukov26-Jun-13 13:33
mvaSergey Alexandrovich Kryukov26-Jun-13 13:33 
GeneralRe: Discussion on Screen Size and MDI Pin
Ron Beyer26-Jun-13 14:03
professionalRon Beyer26-Jun-13 14:03 
GeneralRe: Discussion on Screen Size and MDI Pin
Sergey Alexandrovich Kryukov26-Jun-13 16:55
mvaSergey Alexandrovich Kryukov26-Jun-13 16:55 
SuggestionRe: Discussion on Screen Size and MDI Pin
TnTinMn27-Jun-13 8:00
TnTinMn27-Jun-13 8:00 
GeneralRe: Discussion on Screen Size and MDI Pin
Ron Beyer27-Jun-13 8:39
professionalRon Beyer27-Jun-13 8:39 
GeneralRe: Discussion on Screen Size and MDI Pin
TnTinMn27-Jun-13 13:47
TnTinMn27-Jun-13 13:47 
QuestionCan not load dlls in project Pin
Nooredin25-Jun-13 23:49
Nooredin25-Jun-13 23:49 
AnswerRe: Can not load dlls in project Pin
Eddy Vluggen26-Jun-13 0:11
professionalEddy Vluggen26-Jun-13 0:11 
GeneralRe: Can not load dlls in project Pin
Nooredin26-Jun-13 0:24
Nooredin26-Jun-13 0:24 
GeneralRe: Can not load dlls in project Pin
Eddy Vluggen26-Jun-13 1:12
professionalEddy Vluggen26-Jun-13 1:12 
GeneralRe: Can not load dlls in project Pin
Dave Kreskowiak26-Jun-13 2:23
mveDave Kreskowiak26-Jun-13 2:23 
AnswerRe: Can not load dlls in project Pin
Nooredin26-Jun-13 2:31
Nooredin26-Jun-13 2:31 
QuestionProblem with accessing Asp.net web application through other system Pin
ven75325-Jun-13 20:49
ven75325-Jun-13 20:49 
AnswerRe: Problem with accessing Asp.net web application through other system Pin
Bernhard Hiller25-Jun-13 21:07
Bernhard Hiller25-Jun-13 21:07 
AnswerRe: Problem with accessing Asp.net web application through other system Pin
MaulikDusara26-Jun-13 8:52
MaulikDusara26-Jun-13 8:52 
AnswerRe: Problem with accessing Asp.net web application through other system Pin
Manu V Nath3-Jul-13 23:11
professionalManu V Nath3-Jul-13 23:11 
QuestionExecutable not running from the System32 directory Pin
Dotnetifier24-Jun-13 5:46
Dotnetifier24-Jun-13 5:46 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.