| |
Compyx
Registered: Jan 2005
Posts: 631 |
Release id #212349 : VICE 3.6
Since there are some questions in the comments section of VICE 3.6, I figured it would be better use the forum for any questions.
So to start things off:
Quoting The Human Code MachineBut how can I save the monitor window position on GTK3 Vice Windows x64? After exiting it always opens the same small window.
Currently you can't, window resizing/repositioning support is different across OSes/WMs, so making this work properly for all configurations may never work. That said, I'm working on a "fix" to make it at least work on some systems. |
|
... 65 posts hidden. Click here to view all posts....
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11091 |
That was very long ago, and it should be obvious it causes nothing but problems. You can always remap it that way if you like broken keyboard :) |
| |
Stone
Registered: Oct 2006
Posts: 168 |
Works on real HW! Back in the day when my Restore key stopped functioning, I hardwired it to the Shift Lock key. Worked like a charm! |
| |
chatGPZ
Registered: Dec 2001
Posts: 11091 |
LOL. feel free to create a stones-broken-keyboard.vkm =) |
| |
Endurion
Registered: Mar 2007
Posts: 72 |
It seems the arguments for true drive have changed.
If passing the old version (-/+truedrive -/+virtualdev) VICE simply doesn't startup without any message, just returning 1.
Please, if you don't like the arguments, show some info message about that. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
The -virtualdev option has indeed changed to -virtual[8-11], as has -truedrive, which is now -drive[8-11]truedrive.
VICE does print an error message:
Option '+virtualdev' is ambiguous.
Error parsing command-line options, bailing out. For help use '-help'
So I assume your using Windows, where Microsoft in their infinite wisdom decided to not connect stdout/stderr to the terminal. You can still catch the messages by redirecting stdout/stderr to a file or piping to a program like more. |
| |
JackAsser
Registered: Jun 2002
Posts: 1987 |
Thanks for the 3.6.1 update! Btw does cpu tracing eat so much extra power that it can’t be compiled in by default? Not that it’s hard to compile yourself ofc, just asking out of curiosity. I could also just measure myself… :) Follow up question, I have not digged in that code for a long time but remember I patched in cycle/line tracing also for some project I did, but would it be complicated to have enabling/disabling cpu tracing as a runtime option? |
| |
chatGPZ
Registered: Dec 2001
Posts: 11091 |
"Btw does cpu tracing eat so much extra power that it can’t be compiled in by default?"
It takes almost zero extra effort actually, its just a cyclic buffer, 3 lines of code per CPU cycle. So yeah, the option to disable it can probably be safely removed alltogether :) |
| |
JackAsser
Registered: Jun 2002
Posts: 1987 |
Quote: "Btw does cpu tracing eat so much extra power that it can’t be compiled in by default?"
It takes almost zero extra effort actually, its just a cyclic buffer, 3 lines of code per CPU cycle. So yeah, the option to disable it can probably be safely removed alltogether :)
Thanks for the quick answer GP! Consider that a request then. :) |
| |
Erhan
Registered: Feb 2005
Posts: 17 |
win10pro 19043.1415 locale TR lang TR,
x64sc.exe, both 3.6.0 and 3.6.1
monitor activated, there, it is impossible to type # and $ from keyboard. Shift+3 Shift+4 AltGr+3 AltGr+4 respectively types ^ + <none> <none>. (typing # $ was also a problem in main emulator - default settings - but after editing gtk3_pos.vkm it's normal there) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11091 |
try the build from github, alt-gr in the monitor was fixed. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 - Next |
