Screenshots requested
Re: Screenshots requested
Roger,
This is a screenshot of one of our dialogs
Each of 3 main dialogs (buyer, lot, seller) opens up from the main menu in it's own window/thread. not modal.
My staff has just asked me about the possibility of placing all these dialogs into another window inside our application thusly:
I'm thinking each tab would probably still need to have it's own thread, (to avoid re-writing all the logic coming from each dialogs actions) but from a U.I. POV, it would be very good for our users.
might this be possible ??
This is a screenshot of one of our dialogs
Each of 3 main dialogs (buyer, lot, seller) opens up from the main menu in it's own window/thread. not modal.
My staff has just asked me about the possibility of placing all these dialogs into another window inside our application thusly:
I'm thinking each tab would probably still need to have it's own thread, (to avoid re-writing all the logic coming from each dialogs actions) but from a U.I. POV, it would be very good for our users.
might this be possible ??
Brian Wolfsohn
Retired and traveling around the country to music festivals in my RV.
breadmanbrian@bsky.social
http://www.breadmanrises.com
FB travel group: The Breadman Rises
Retired and traveling around the country to music festivals in my RV.
breadmanbrian@bsky.social
http://www.breadmanrises.com
FB travel group: The Breadman Rises
Re: Screenshots requested
That's an interesting idea and I think it is possible.I'm thinking each tab would probably still need to have it's own thread,
(to avoid re-writing all the logic coming from each dialogs actions) but from a U.I. POV,
it would be very good for our users.
might this be possible ??
I will work on a sample program.
The eXpress train is coming - and it has more cars.
Re: Screenshots requested
Hi,
I thought about this some weeks ago. Using TAB pages is a nice look and feel. A problem I see is that a user can now open easily the same function/thread several times. Then he can move the dialog to the place he wants. When using tab-pages, it won't be possible to do this?
This is the look I made. I'm wondering how a user could open Customers (klanten) two times. Now it opens two dialogs in a different thread.
The 'tabpages' are in fact buttons on a toolbar. The height of the toolbar is 38, at row 12 I put buttons with a height of 30. This way they look as a tab.
I thought about this some weeks ago. Using TAB pages is a nice look and feel. A problem I see is that a user can now open easily the same function/thread several times. Then he can move the dialog to the place he wants. When using tab-pages, it won't be possible to do this?
This is the look I made. I'm wondering how a user could open Customers (klanten) two times. Now it opens two dialogs in a different thread.
The 'tabpages' are in fact buttons on a toolbar. The height of the toolbar is 38, at row 12 I put buttons with a height of 30. This way they look as a tab.
Re: Screenshots requested
when start with Codejock Control we realize that Windows "real" Tabpage ist different to Alaska XbpTabpage()
Windows API does have a TabControl ( WC_TABCONTROL ) but there is no "Body" ...
we did add a XbpStatic as Parent for Xbase++ and use SetParent() API to attach it to TabControl.
TabControl just switch Tabs and Hide()/Show() "Body" so in general it is possible to use a XbpDialog instead of XbpStatic as "Body"
Windows API does have a TabControl ( WC_TABCONTROL ) but there is no "Body" ...
we did add a XbpStatic as Parent for Xbase++ and use SetParent() API to attach it to TabControl.
TabControl just switch Tabs and Hide()/Show() "Body" so in general it is possible to use a XbpDialog instead of XbpStatic as "Body"
greetings by OHR
Jimmy
Jimmy
Re: Screenshots requested
I am working on a sample now.
It will probably require a few small changes to eXpress++ to insure that each thread stops when the dialog is closed.
I created a dialog with 3 tabs and then called the same program 3 times in 3 threads to put child items on the tabs.
This requires running 4 event loops, 1 for the main window and 1 for each thread. It appears to be working and should require minor changes to your code. I hope to have something for you to look at this morning.
It will probably require a few small changes to eXpress++ to insure that each thread stops when the dialog is closed.
I created a dialog with 3 tabs and then called the same program 3 times in 3 threads to put child items on the tabs.
This requires running 4 event loops, 1 for the main window and 1 for each thread. It appears to be working and should require minor changes to your code. I hope to have something for you to look at this morning.
The eXpress train is coming - and it has more cars.
Re: Screenshots requested
Brian and Chris -
I think this is what you asked for.
http://bb.donnay-software.com/donnay/vi ... 8078#p8078
I think this is what you asked for.
http://bb.donnay-software.com/donnay/vi ... 8078#p8078
The eXpress train is coming - and it has more cars.
Re: Screenshots requested
Hi,
Here is some of our screens from Restoraunt touchscreen Sw and retail sw
Here is some of our screens from Restoraunt touchscreen Sw and retail sw
- Attachments
-
- Screens.zip
- (1.19 MiB) Downloaded 1560 times
Goran Radosic
Re: Screenshots requested
Nolberto Paulino
DIGISOFT AYCONT, SRL.
DIGISOFT AYCONT, SRL.
- Attachments
-
- Punto de Venta.jpg (175.92 KiB) Viewed 58392 times
-
- Menu Punto de Venta.jpg (286.91 KiB) Viewed 58392 times
Nolberto Paulino
Regards
Regards
- sdenjupol148
- Posts: 151
- Joined: Thu Jan 28, 2010 10:27 am
- Location: NYC
Re: Screenshots requested
Hi All,
I am happy to see that you all have been putting eye-catching and thoughtful work into your applications.
But as I sit here and thoroughly enjoy these screen shots, it occurred to me that no one is showing the other awesome part of express which is the print engine.
So I decided to show print preview shots instead.
These are not using PDF, activeX or any other third party preview or presentation space assembly engines.
These are 100% eXpress++/DCPRINT commands using the DCPRINT PREVIEW option straight.
They are easy to put together and resulting printout looks exactly like the preview.
If anyone would like to see the code behind it, come to the Idaho DevCon and I'll be happy to share.
The first two previews are of the receipt (front page and back page) from the Medallion NYC application.
The third preview is a mechanics work order from the TLC Repair Shop application
Bobby
I am happy to see that you all have been putting eye-catching and thoughtful work into your applications.
But as I sit here and thoroughly enjoy these screen shots, it occurred to me that no one is showing the other awesome part of express which is the print engine.
So I decided to show print preview shots instead.
These are not using PDF, activeX or any other third party preview or presentation space assembly engines.
These are 100% eXpress++/DCPRINT commands using the DCPRINT PREVIEW option straight.
They are easy to put together and resulting printout looks exactly like the preview.
If anyone would like to see the code behind it, come to the Idaho DevCon and I'll be happy to share.
The first two previews are of the receipt (front page and back page) from the Medallion NYC application.
The third preview is a mechanics work order from the TLC Repair Shop application
Bobby
- Attachments
-
- receipt.jpg (734.42 KiB) Viewed 58380 times
-
- receipt page 2.jpg (1.19 MiB) Viewed 58380 times
-
- mechanics service order.jpg (1.31 MiB) Viewed 58380 times
Last edited by sdenjupol148 on Sun Apr 12, 2015 3:24 pm, edited 1 time in total.
- sdenjupol148
- Posts: 151
- Joined: Thu Jan 28, 2010 10:27 am
- Location: NYC
Re: Screenshots requested
These two previews are of the delivery slip and invoice printout from the PR Transport application
- Attachments
-
- transport delivery slip2.jpg (208.45 KiB) Viewed 58380 times
-
- transport invoice2.jpg (160.97 KiB) Viewed 58380 times