|
|
Post by Janet on May 5, 2018 16:08:21 GMT -5
I don't think there will be any pitfalls in removing UpperLeftX and UpperLeftY, but you'd be way more familiar with your users' activity than I would. I added a SetParent API call and a MoveWindow API call and this may be more in keeping what you want. I changed it from a dialog_popup to a window_popup. Not sure it makes a difference either way, but I didn't see a need for a dialog window if it were going to become a child. I'm a little concerned that at least one textbox is 'showing through' on some of the wider tooltips, so it still needs tweaking. Also, in your [quit] routine, you'll want to check if ttFlag = 1 and if it is, then close #tt.
'=========================================================================================================
[RightClickButton] ' graphic 5 , yyy, bttnWidth, bttnHeight
x=val(Tip$(BU,7)) : y=val(Tip$(BU,8)) :bttnWidth=val(Tip$(BU,9)) : bttnHeight=val(Tip$(BU,10))
if ttFlag = 1 then
close #tt
ttFlag = 0
end if
'=========================================================================================================
' Set Popup box and window size--- Need good algorithim
'=========================================================================================================
ttWindowWidth = int(6.3 * Cntrs(BU,2)+20) ' set popup width size maxlinewidth * 6.5
ttWindowHeight =int(20 * Cntrs(BU,1)+35) ' set popup height size Linecnt*20
'---------------------------------------------------------------------------------------------------------
WindowWidth = ttWindowWidth ' Define the pseudo-tooltip window
WindowHeight = ttWindowHeight ' SET EQUAL TO POPUP SIZE !!!!!!!!
'=========================================================================================================
'graphicbox #tt.g 0, 0, ttWindowWidth,ttWindowHeight ' Define a pseudo-tt graphicbox
graphicbox #tt.g 0, 0, ttWindowWidth,ttWindowHeight ' Define a pseudo-tt graphicbox
stylebits #tt, 0,_WS_BORDER,_WS_EX_TOPMOST,0 ' Remove borders and make stay on top with stylebits
open "" for window_popup as #tt ' Open the window as a dialog_popup
ttFlag = 1
#tt "trapclose [closettWindow]"
'---------------------------------------------------------------------------------------------------------
' may need locate
'jlt-------------------------
'Make this new window a child window
hChild = hwnd(#tt)
hParent = hwnd(#main)
calldll #user32, "SetParent", _
hChild as ulong, _
hParent as ulong, _
result as long
' Move the window to desired location
x = 10 : y = BU*25 - 15
calldll #user32, "MoveWindow", _
hChild as ulong, _
10 as long, _
y as long, _
ttWindowWidth as long, _
ttWindowHeight as long, _
1 as long, _
result as long
'' #tt.g "locate ";x;" ";y
#tt.g "down"
#tt.g "fill 255 240 210"
#tt.g "backcolor 255 240 210" ' color tooltip
#tt.g "place 10 15; font Garamond_14" ' Write something in the tooltip
#tt.g "\";R$(BU) ' RU(BU) Tool Tip Data
''#tt.g "\";crlf$;crlf$;"Left-click-here to close"
'---------------------------------------------------------------------------------------------------------
#tt.g "when leftButtonUp [closettWindow]" ' Send left-click to trapclose
goto [LoopEnter] ''wait
|
|
xtal
Junior Member
Posts: 61
|
Post by xtal on May 9, 2018 19:36:23 GMT -5
I'm having a problem displaying total tool tip unless I make the gui window bigger....[$Nxx.txt] main culprit. I made the lines longer but for some reason Line input wants to keep it like it was, can't figure that. Tried Line input then print to window, same result lines are not same lenth as notepadd++ displays??? The pgm I testing with attached.... tooltip-modal2.zip (8.52 KB) For some reason Notepad++ apparently wasn't saving correctly , but after another edit the $N window now window fits and moves ok if you move mainwin... GREMLIN's are in our mist........ In my actual program with comm Open The upper 4 buttons ---> their info/tips are being overlayed with the DRO's[digital readout's] when the readouts are updated... What do about that??? Other than block the DRO display update while popup active. |
|
|
|
Post by Janet on May 10, 2018 8:39:32 GMT -5
I'm having a problem displaying total tool tip unless I make the gui window bigger....[$Nxx.txt] main culprit. I made the lines longer but for some reason Line input wants to keep it like it was, can't figure that. Tried Line input then print to window, same result lines are not same lenth as notepadd++ displays??? The pgm I testing with attached.... For some reason Notepad++ apparently wasn't saving correctly , but after another edit the $N window now window fits and moves ok if you move mainwin... GREMLIN's are in our mist........ In my actual program with comm Open The upper 4 buttons ---> their info/tips are being overlayed with the DRO's[digital readout's] when the readouts are updated... What do about that??? Other than block the DRO display update while popup active. So the display size is okay now? I also noted that the readout numbers were showing through. I think your blocking update while popup active solution is the best bet. |
|
xtal
Junior Member
Posts: 61
|
Post by xtal on May 10, 2018 18:20:25 GMT -5
so no magic style bits !
|
|
|
|
Post by Rod on May 11, 2018 1:18:31 GMT -5
If you move the cursor the button frames show through as well. So I would be thinking that the stylebit code is not being applied or is lost in the subsequent handling of the tooltip window.. try using a simple window in a fixed position, then move it, then color iit with a graphicbox and see where the stylebit is being lost.
|
|
|
|
Post by Rod on May 11, 2018 7:33:24 GMT -5
I made a few changes. It was attaching the tooltip window as a child of the main window that lost the stylebits. I set UpperleftX and UpperLeftY, got rid of the child window code and used UpperLeftX and UpperLeftY to set the position of the tooltip window.
'========================================================================================================
' Define the main window
'--------------------------------------------------------------------------------------------------------
[WindowSetup]
'nomainwin
WindowWidth = mainWindowWidth
WindowHeight = mainWindowHeight
UpperLeftX = (DisplayWidth-WindowWidth)/2
UpperLeftY = (DisplayHeight-WindowHeight)/2
graphicbox #tt.g 0, 0, ttWindowWidth,ttWindowHeight ' Define a pseudo-tt graphicbox
stylebits #tt, 0,_WS_BORDER,_WS_EX_TOPMOST,0 ' Remove borders and make stay on top with stylebits
'' open "" for dialog_popup as #tt ' Open the window as a dialog_popup
open "" for window_popup as #tt ' Open the window as a dialog_popup
ttFlag = 1
#tt "trapclose [closettWindow]"
'jlt-------------------------
'Make this new window a child window
hChild = hwnd(#tt)
'hParent = hwnd(#main)
'calldll #user32, "SetParent", _
' hChild as ulong, _
' hParent as ulong, _
' result as long
' Move the window to desired location
x = UpperLeftX+40 : y = UpperLeftY+BU*25 - 15
calldll #user32, "MoveWindow", _
hChild as ulong, _
x as long, _
y as long, _
ttWindowWidth as long, _
ttWindowHeight as long, _
1 as long, _
result as long
I would have thought that you would want to suspend operations and serial interaction if tooltips are on display.
|
|
xtal
Junior Member
Posts: 61
|
Post by xtal on May 14, 2018 13:14:30 GMT -5
I really saw no reason to stop the program to read info/tool tip...
I tried the above code , the tooltip/info pops up on left side of display - away from my window.
When I move the window the tooltip/info doesn't move, stays toward left side of screen
|
|
|
|
Post by Rod on May 14, 2018 13:38:59 GMT -5
The tooltip positioned correctly for me, be sure the upper and lower case are correct naming the variables. I have always said in the past that you should pick a window size that fits your program. Trying to accommodate window movements and resizing adds massive complications. Get it pixel perfect for the task in hand and keep it that way.
If a program runs in 800x600 I am happy. If it runs 1028,768 I am happy, if it grabs full screen I am less happy. If it runs bigger than my screen it will never get fired up.
So how many pixels do you really need? How many pixels to show off the cutting path? How many steps, what resolution, how to scale the view? You can dance to the users tune or you can dictate what is seen.
|
|
xtal
Junior Member
Posts: 61
|
Post by xtal on May 14, 2018 16:47:50 GMT -5
What I see is the tooltip positions relative to UpperLeftX and UpperLeftY
So when I move the window [Drag to screen 2] I need to change UpperLeftX and UpperLeftY
How do I determine where my UL corner of my window is so I can
update UpperLeftX and UpperLeftY to compensate for my new position...
How do I determine UL window corner...
And Yes the DRO's do not show in the tool tips...
Tried the following , had no success
'create the structure winRect
struct winRect, _
orgX as long, _
orgY as long, _
cornerX as long, _
cornerY as long
'get the window handle for #main (a standard Liberty BASIC window)
hMain = hwnd(#main)
'call the GetWindowRect API to load the window position/size into winRect
calldll #user, "GetWindowRect", _
hMain as long, _
winRect as struct, _
result as boolean
'extract the position information out of our struct
xOrg = winRect.orgX.struct
yOrg = winRect.orgY.struct
'----------- runtime error No DLL for #user see error log
added x=xOrg+MouseX : y=yOrg+MouseY+BU*25-15
now ok as long as you close the tip before moving the window
|
|
xtal
Junior Member
Posts: 61
|
Post by xtal on May 14, 2018 18:01:20 GMT -5
so with Janets code I can open a tool tip , move the window , and tool tip moves also, how ever
The DRO updates bleed thru , thus requiring 5 lines of code to bypass while ttFlag is on.
with Rod's code after my addition , I can move the window and the tool tip will popup within my window,
however a currently displaying tool tip will not move with the window, but there is no DRO bleed thru..
decision's decision's decision's
|
|
xtal
Junior Member
Posts: 61
|
Post by xtal on May 15, 2018 12:06:40 GMT -5
I've discovered some more bleed thru issues , so will go with Rod's change and tolerate that an open tooltip will not move
when you move the window, this is just an minor issue...
|
|
