|
|
Post by pablosl on Jan 31, 2019 19:15:04 GMT -5
1) CHAIN command like quickbasic, to pass program control to other program, wait for it to end and then gain control again.
2) Keyboard shortcuts for menus.
3) Hyperlink control
|
|
|
|
Post by Carl Gundel on Feb 1, 2019 17:19:38 GMT -5
1) CHAIN command like quickbasic, to pass program control to other program, wait for it to end and then gain control again. 2) Keyboard shortcuts for menus. 3) Hyperlink control CHAIN - You mean with the sharing of variables between programs? I think that running another program and passing values to it will be possible, but that not exactly the same thing. Key shortcuts - Exactly what do you want to do that you cannot do now? Hyperlink control - What do you mean by this? |
|
|
|
Post by Chris Iverson on Feb 1, 2019 18:23:34 GMT -5
Key shortcuts - Exactly what do you want to do that you cannot do now? Based on what he said, I think he means keyboard menu accelerators, like these:  Hyperlink control - What do you mean by this? I think he means something like a statictext that "activates" when clicked on. This can at least be faked with a graphicbox; draw the text in the place and style you want, and add a click handler to the box. |
|
|
|
Post by pablosl on Feb 4, 2019 18:11:26 GMT -5
@carl:
1) Chris is right in both things, I mean keyboard menu accelerators to show the user that when he/she press F1 the program open the helpfile.
2) And hyperlink is a statictext that shows itself in blue color but when the mouse cursor is over the widget is then underlined, and when the user click it, this action open the desired webpage in the default internet browser.
3) And about CHAIN statement, yeah, not only to exchange variables between programs. I would like my window #1(type window, which have menus and toolbar) CALL a second window (type modal dialog) to enter i.e. user data information like Name, Address and City. When the user click the button OK in this window #2, then the second window (program) is closed and ENDs, and then the window #1 has focus again.
-Pablo
|
|
|
|
Post by Brandon Parker on Feb 4, 2019 18:44:06 GMT -5
Pablo,
You should already be able to achieve #3 easily in Liberty Basic. You can open many windows at any time during a program's execution and make any of them a Dialog Modal window or similar to achieve what you are describing. You wouldn't need a second complete program for what you are describing.
Sample code ...
NoMainWin
'Set up and Open the Main Window
Button #MainWindow.btnOpenSecondary, "Open Secondary Window", openSecondaryWindow, UL, 50, 50, 140, 25
Button #MainWindow.btnClose,"Close Window", quit, UL, 50, 80, 120, 25
Open "Main Window" For Window As #MainWindow
#MainWindow "TrapClose quit"
Wait
'Generic Quit handler which will handle both windows and
'"Quit/ Close Buttons" for Windows like the Secondary Window below
'which has had it's System Menu removed
Sub quit handle$
If Instr(handle$, ".") Then handle$ = Word$(handle$, 1, ".")
Close #handle$
If (handle$ = "#MainWindow") Then End
End Sub
'Subroutine for opening a secondary window as Dialog_Modal which
'forces it to be on top of the parent window which is the
'Main Window in this case.
Sub openSecondaryWindow handle$
Button #SecondaryWindow.btnClose,"Close Window", quit, UL, 50, 50, 120, 25
Stylebits #SecondaryWindow, 0, _WS_SYSMENU, 0, 0
Open "Secondary Window" For Dialog_Modal As #SecondaryWindow
#SecondaryWindow "TrapClose quit"
End Sub
{:0)
Brandon Parker
|
|
|
|
Post by Carl Gundel on Feb 5, 2019 9:09:58 GMT -5
Pablo, You should already be able to achieve #3 easily in Liberty Basic. You can open many windows at any time during a program's execution and make any of the a Dialog Modal window or similar to achieve what you are describing. You wouldn't need a second complete program for what you are describing. +1. There really is no practical limit to the number of Windows that you can open in a Liberty BASIC program. You may not need to chain things together. |
|
