Products > Test Equipment
Oscilloscope Zoom Out Quirk
Elasia:
--- Quote from: tautech on June 14, 2020, 10:15:43 am ---
Elasia's solution I believe is to use the primary timebase of the Zoom mode framework but hidden as the basis for capture zoom out.
Max memory depth selected for ordinary Zoom mode would work as normal but could be toggled to a hidden Zoom UI and then provide capture zoom out capability from the full mem depth the user has set.
Is that right Elasia ?
--- End quote ---
Correct, you use the code base of zoom mode but are just hiding the shown UI components and rescaling the zoom area to full screen
And you don't get rid of either, you allow the user to use split screen or hide what they want... in the end its all functions of telescopic zooming people are doing, only thing going around and around are semantics of what it looks like
Elasia:
--- Quote from: SilverSolder on June 14, 2020, 12:51:16 pm ---
--- Quote from: 2N3055 on June 14, 2020, 11:35:13 am ---
[...]
Used Pico as example:
[...]
--- End quote ---
The "root cause" of the whole discussion is that the typical oscilloscope doesn't have a very big screen, so the various zooming ideas being discussed are essentially ways to overcome that in a smooth and convenient way.
Having the scope run on your PC gives you a whole bunch of new advantages, obviously. With a comparatively gigantic screen, you can have several windows open with different degrees of zoom.
On the other hand, a PC based scope requires that you are totally comfortable with a mouse-and-keyboard workflow, rather than physical knobs. Personally, I like both approaches!
--- End quote ---
Which i find ironic in the case of the 2k+... while i dont like the real estate consumed by the horizontal scrollbar.. it also isnt a hindrance other than its more data on the screen i dont need to immediately be looking at so for me it works fine as is.. my only adovation is for hiding the extra ui bits so i get more screen space back... which also just happens to be the more natural way to zoom in and out / control memdepth to timebase
tautech:
--- Quote from: Elasia on June 14, 2020, 01:12:09 pm ---
--- Quote from: tautech on June 14, 2020, 10:15:43 am ---
Elasia's solution I believe is to use the primary timebase of the Zoom mode framework but hidden as the basis for capture zoom out.
Max memory depth selected for ordinary Zoom mode would work as normal but could be toggled to a hidden Zoom UI and then provide capture zoom out capability from the full mem depth the user has set.
Is that right Elasia ?
--- End quote ---
Correct, you use the code base of zoom mode but are just hiding the shown UI components and rescaling the zoom area to full screen
And you don't get rid of either, you allow the user to use split screen or hide what they want... in the end its all functions of telescopic zooming people are doing, only thing going around and around are semantics of what it looks like
--- End quote ---
Of course not. ;)
What will be interesting is exactly how it's implemented. Zoom in and Zoom out capture capabilities !
When I have some more 2kX Plus hopefully I'll get see a beta of the proposed solution but it's a little way off yet.
Existing strategies will not apparently be changed only capture memory management.
Elasia:
--- Quote from: tautech on June 14, 2020, 01:22:38 pm ---
--- Quote from: Elasia on June 14, 2020, 01:12:09 pm ---
--- Quote from: tautech on June 14, 2020, 10:15:43 am ---
Elasia's solution I believe is to use the primary timebase of the Zoom mode framework but hidden as the basis for capture zoom out.
Max memory depth selected for ordinary Zoom mode would work as normal but could be toggled to a hidden Zoom UI and then provide capture zoom out capability from the full mem depth the user has set.
Is that right Elasia ?
--- End quote ---
Correct, you use the code base of zoom mode but are just hiding the shown UI components and rescaling the zoom area to full screen
And you don't get rid of either, you allow the user to use split screen or hide what they want... in the end its all functions of telescopic zooming people are doing, only thing going around and around are semantics of what it looks like
--- End quote ---
Of course not. ;)
What will be interesting is exactly how it's implemented. Zoom in and Zoom out capture capabilities !
When I have some more 2kX Plus hopefully I'll get see a beta of the proposed solution but it's a little way off yet.
Existing strategies will not apparently be changed only capture memory management.
--- End quote ---
lol does defprom still have yours?
tautech:
--- Quote from: Elasia on June 14, 2020, 01:39:45 pm ---
--- Quote from: tautech on June 14, 2020, 01:22:38 pm ---
--- Quote from: Elasia on June 14, 2020, 01:12:09 pm ---
--- Quote from: tautech on June 14, 2020, 10:15:43 am ---
Elasia's solution I believe is to use the primary timebase of the Zoom mode framework but hidden as the basis for capture zoom out.
Max memory depth selected for ordinary Zoom mode would work as normal but could be toggled to a hidden Zoom UI and then provide capture zoom out capability from the full mem depth the user has set.
Is that right Elasia ?
--- End quote ---
Correct, you use the code base of zoom mode but are just hiding the shown UI components and rescaling the zoom area to full screen
And you don't get rid of either, you allow the user to use split screen or hide what they want... in the end its all functions of telescopic zooming people are doing, only thing going around and around are semantics of what it looks like
--- End quote ---
Of course not. ;)
What will be interesting is exactly how it's implemented. Zoom in and Zoom out capture capabilities !
When I have some more 2kX Plus hopefully I'll get see a beta of the proposed solution but it's a little way off yet.
Existing strategies will not apparently be changed only capture memory management.
--- End quote ---
lol does defprom still have yours?
--- End quote ---
Nope. :(
Got sold before I even got it back.....and we were in Covid lockdown at the time !
The moment it came back, in the mail again it went to its new owner.
So now I just have to use a SDS5054X. ;D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version