Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Recent content by vefatica

  1. vefatica

    ON BREAK LEAVE?

    So breaking from a delay leaves you inside the DO and breaking from the previous command doesn't (or something like that).
  2. vefatica

    ON BREAK LEAVE?

    ON BREAK LEAVE - is it cool? Sometimes I get an error; sometimes I don't. v:\> type zerotest.btm setlocal on break leave do forever set ticks=%@winapi[kernel32,GetTickCount] if %@eval[%_do_loop MOD 10000] == 0 echo %_do_loop %ticks enddo v:\> zerotest.btm 10000 812419140 ^C v:\>...
  3. vefatica

    WAD @WINAPI with PINT64 gives only the high DWORD

    Thanks for that. I already have a plugin _AGENOW which does it. FWIW ... I had a little fun getting around my difficulty with another plugin that might come in handy again. v:\> help @buftoint @BUFTOINT[buffer,size] size = 1, 2, 4, 8 It's 10 lines of code with memcpy doing the work...
  4. vefatica

    WAD @WINAPI with PINT64 gives only the high DWORD

    I don't know enough to comment further. This thread grew out of my desire to use @WINAPI on GetSystemTimePreciseAsFileTime.
  5. vefatica

    WAD @WINAPI with PINT64 gives only the high DWORD

    The API wrote 1DD77C7 somewhere and @WINAPI returned it. How did that happen? I don't mind being wrong (I do that a lot) as long as I learn from it.
  6. vefatica

    WAD @WINAPI with PINT64 gives only the high DWORD

    Then what's happening here? GetSystemTimePreciseAsFileTime is writing something at a location given to it by TCC, and whats being echo'd is exactly equal to the high DWORD of the precise system time as a file time. v:\> echo %@eval[%@winapi[kernel32,GetSystemTimePreciseAsFileTime,pint64]=h]^...
  7. vefatica

    WAD @WINAPI with PINT64 gives only the high DWORD

    Huh! What's PINT64 all about? And what syntax is wrong?
  8. vefatica

    WAD @WINAPI with PINT64 gives only the high DWORD

    Interesting! But I dunno. At least with @WINAPI, the buffers (pint, ... buffer, abuffer) are typed. So you get some help getting useful data out. Actually, I'm using this. set agenow=%@eval[%@makeage[%_date,%_time] + %_tzo * 60 * 10000000] If pint64 were working correctly @WINAPI would...
  9. vefatica

    WAD @WINAPI with PINT64 gives only the high DWORD

    Given how I'm processing it when I use "buffer", isn't it binary to begin with? How else might it work?
  10. vefatica

    Can't get TCC to render text on a black background

    As you probably know there are simpler SGR control sequences that can do the job but they're likely to depend on the current 16-color palette. In any event, I think SGR control sequences are a safer way to go than the COLOR command
  11. vefatica

    WAD @WINAPI with PINT64 gives only the high DWORD

    @Joe Caverly, nice!. I can (sort of) work around it by using buffer instead of pint64 and deciphering the buffer myself. v:\> set x=%@unicode[%@winapi[kernel32,GetSystemTimePreciseAsFileTime,buffer]] & set y=%_agenow v:\> echo %@eval[(%@word[3,%x] * 2**48) + (%@word[2,%x] * 2**32) +...
  12. vefatica

    WAD @WINAPI with PINT64 gives only the high DWORD

    Below, _AGENOW uses GetSystemTimePreciseAsFileTime. @WINAPI gives only the high DWORD. v:\> echo %@winapi[kernel32,GetSystemTimePreciseAsFileTime,pint64] 31291232 v:\> echo %@eval[31291232=h] 1DD7760 v:\> echo %@eval[%_agenow=h] 1DD77604DA271FD
  13. vefatica

    Saving the TCC Console as HTML to RightNote

    Hmmm! With KEYSTACK you might be able to turn one of these into a command. While thinking about that, I noticed that Alt+H doesn't open the Home menu or the Help menu (odd that they both use H); whereas Alt+accelerator does open all the other menus.
  14. vefatica

    How do you define a custom color scheme?

    I have the TabColorNNs set to my modified Ottosson WT theme. But when I tell TCMD to use "(Custom)" theme I get the age-old 16 color console palette. I'm not sure how it all works.
  15. vefatica

    Does @REGSET support REG_QWORD?

    It does! That's good news. You need it for FILETIMEs. So the type spec is REG_QWORD?
Back
Top