|
Post by xxgeek on Nov 17, 2021 16:02:13 GMT -5
2 things I noticed in the last couple of days..
Using & to underscore a character for Hotkey no longer shows the _ underline when code is run. The hotkey(s) still work though.
Also, I have been using: run "taskmgr" and/or run "taskmgr.exe" to open the windows task manager in some code. It used to work (until a couple of days ago) - Thanks to .dan1101 for pointing it out in the Liberty Help Lab and Project Organizer. Now I'm getting "out of memory" errors using the exact same code line.
What's next? JB and LB stop working some day? I wish Microsoft would call me before they change something like this.
The basta(nevermind)
Off to research the "new" way to open taskmanager ............
|
|
|
Post by tsh73 on Nov 17, 2021 16:52:44 GMT -5
Interesting Out of memory happened with me too, Win10 32
This thing worked
run "explorer taskmgr.exe"
|
|
|
Post by xxgeek on Nov 17, 2021 17:14:45 GMT -5
Interesting Out of memory happened with me too, Win10 32 This thing worked run "explorer taskmgr.exe" Thanks tsh73 that didn't work here on Win 10 Pro 64bit. It opened into an explorer window @ Documents. BUT, it did lead to some testing and Run "explorer c:\Windows\System32\taskmgr.exe" Works like a champ using full path. Thanks for posting tsh73. I had tried so many variations of cmd and start without success, I had rewrote my code to "Press Cntrl + Shift + Esc Simultaneouly so the user could at least get taskman opened lol Thinking outside the box with persistence usually gets the job done. 2 minds are always better than 1
|
|
|
Post by Chris Iverson on Nov 17, 2021 17:59:56 GMT -5
That's... extremely weird.
Here's the error log created by RUN "taskmgr.exe"
Error log timestamp Wednesday 11/17/21 04:58:49 PM
Runtime error: out of memory
Error(Exception)>>defaultAction Error(Exception)>>activateHandler: <anUndefinedObject> Error(Exception)>>handle Error(Exception)>>signal Error class(Exception class)>>signal: <'out of memory'> BasicProgram(Object)>>error: <'out of memory'> BasicProgram>>terminateRun: <anError> [] in BasicProgram>>errorHandlerBlock ExceptionHandler>>evaluateResponseBlock: <aBlockClosure> for: <anError> [] in ExceptionHandler>>handle: ProtectedFrameMarker(BlockClosure)>>setUnwind: <aBlockClosure> BlockClosure>>invisibleEnsure: <aBlockClosure> ExceptionHandler>>handle: <anError> ExceptionHandler>>findHandler: <anError> Error(Exception)>>activateHandler: <anExceptionHandler> Error(Exception)>>handle Error(Exception)>>signal Error class(Exception class)>>signal: <'out of memory'> BasicProgram(Object)>>error: <'out of memory'> [] in RunCommand>>using: [] in BasicProgram>>begin ExceptionHandler>>evaluateProtectedBlock: <aBlockClosure> [] in ExceptionHandler>>activateDuring: ProtectedFrameMarker(BlockClosure)>>setUnwind: <aBlockClosure> BlockClosure>>invisibleEnsure: <aBlockClosure> ExceptionHandler>>activateDuring: <aBlockClosure> ExceptionHandler class>>handle: <anError class> with: <aBlockClosure> during: <aBlockClosure> BlockClosure>>on: <anError class> do: <aBlockClosure> BasicProgram>>begin BasicProgram>>run [] in BasicSourcePane>>run BasicCompiler class>>compileFromString: <'run "taskmgr.exe" '> notify: <aBasicSourcePane> ifSuccess: <aBlockClosure> BasicSourcePane>>run BasicSourceWindow>>run BasicEditorModel>>run: <aToolbarButton> BasicEditorModel(Object)>>perform: <#run:> with: <aToolbarButton> ToolbarButton>>triggerClickedEvent Message>>perform NotificationManager>>runPendingEvents NotificationManager>>runEventLoop Message>>perform Message>>evaluate Process>>safelyEvaluate: <aMessage> Process>>evaluate: <aMessage>
EDIT: And it gets weirder. After I closed LB after it crashed, I got an option to run with compatibility settings. So I tried it, and it works... but I can't tell what compatibility settings were applied. If I check the settings manually, it seems like nothing's enabled.
|
|
|
Post by xxgeek on Nov 17, 2021 18:25:56 GMT -5
@ Chris In Linux/WINE the _ underscore works as usual and the taskmanager opens with run "taskmgr" same as always.
I am just assuming... I believe WINE environment is a basic XP like environment. Not tue XP, but close enough to act like it. I get the OLD taskmanager in Linux/WINE
I'm in a 64 bit Linux OS (Mint) with 32 bit support installed manually. Also had to install wsh57 from the winetricks app to get scripting support.
|
|
|
Post by Brandon Parker on Nov 17, 2021 21:17:44 GMT -5
Interestingly, neither of these errors pop up for me. Everything seems to be working except that an "Explorer" window is opened. The Task Manager is opened using the full path as Anatoly posted. I am running: Liberty BASIC - v4.5.1 Edition - Windows 10 Home Version - 20H2 OS build - 19042.1348 Experience - Windows Feature Experience Pack 120.2212.3920.0 Processor - Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz 1.99 GHz Installed RAM - 16.0 GB (15.9 GB usable) System type - 64-bit operating system, x64-based processor It does look like my explorer.exe was updated on 11 Nov 2021, so maybe that has something to do with what is happening? EDIT: After I ran the program, errors and all trying different things, LB did not crash. I went on to run some more code in the same IDE (i.e. process) that was used for the testing, and everything worked as expected. When I closed the LB IDE, I received the message shown below. {:0) Brandon Parker
|
|
|
Post by Chris Iverson on Nov 17, 2021 23:38:33 GMT -5
I had the same exact thing happen on my home PC. Huh.
|
|
|
Post by tsh73 on Nov 18, 2021 2:56:30 GMT -5
Got same window on JB 2.0 yesterday was not able to see what compatibility settings changed or applied, either.
|
|
|
Post by Carl Gundel on Nov 18, 2021 7:44:27 GMT -5
This is what happens when systems try to be too clever, I think. Perhaps Microsoft will figure out a way to make whatever they're doing here more seamless, hopefully?
|
|