Activity for Marky Mark
-
Marky Mark modified a comment on discussion VirtuaWin questions
You can use Visual Basic to start a program running without any visible window. Let's say you want to run C:\Users\MyUsername\MySpecialProgram.exe; then create someNameOrOther.vbs containing: Dim WinScriptHost Set WinScriptHost = CreateObject("WScript.Shell") WinScriptHost.Run Chr(34) & "C:\Users\MyUsername\MySpecialProgram.exe" & Chr(34), 0 Set WinScriptHost = Nothing then just run that vbs file to start the program. Or if you want it to run hidden away whenever the PC starts then go to the system...
-
You can use Visual Basic to start a program running without any visible window. Let's say you want to run C:\Users\MyUsername\MySpecialProgram.exe; then create someNameOrOther.vbs containing: Dim WinScriptHost Set WinScriptHost = CreateObject("WScript.Shell") WinScriptHost.Run Chr(34) & "C:\Users\MyUsername\MySpecialProgram.exe" & Chr(34), 0 Set WinScriptHost = Nothing then in the system Startup folder add a shortcut to the full path of your someNameOrOther.vbs. Then your program will run hidden...
-
Thanks guys. Got to love those one-line fixes.
-
Ah I know more than I would like to about the difficulties of layout constraints, having played around with attachment resources. I'm not entirely convinced that there is no elegant solution, certainly using Motif widgets and suitable containers, although perhaps you don't have enough control via Tk. I might learn more and experiment. Your preference suggestion works for me and I will run with that on the whole, but you might want to take another look at the issue given this screenshot of a partially...
-
I meant a vertical resize to a smaller vertical dimension. I observe that resizing it vertically back to its original size makes the status line re-appear. Maybe there's just some minimal-height constraint on the main diff panel?
-
Status line goes missing on vertical resize
-
There were no prior actions. it just came straight up like that. Using Magnifier, I note that the top of the first diff region (line 9) is mis-aligned by the thickness of the black border surrounding the text area, but that bottom of that first diff region is not mis-aligned. Then the top of the second diff region is similarly mis-aligned and the bottom of that region is mis-aligned by 8 times the thickness of that black border i.e. border-thickness * (n-1) where n is the number of lines in the diff...
-
Mis-alignment between line-no/change-bar panels and file contents
-
With "Ignore Blank Lines" set and saved, get error on startup
-
"Error: 1" when setting Ignore Blank Lines
-
Yes, this problem arose when I started with both the "Ignore blanks when diffing" and "Suppress diffs of empty lines" Preference settings on and then toggled View->ShowChangeBars from off to on. The same thing happens if I toggle it in Preferences. Yes, it was after #61. That describes what I see immediately on startup. I forgot to supply the error details before, although Cbg occurs only in the one place I think; still, here it is: can't read "Cbg": no such variable can't read "Cbg": no such variable...
-
Yes, this problem arose when I started with both the "Ignore blanks when diffing" and "Suppress diffs of empty lines" Preference settings on and then toggled View->ShowChangeBars from off to on. The same thing happens if I toggle it in Preferences. Yes, it was after #61. That describes what I see immediately on startup. I forgot to supply the error details before, although Cbg occurs only in the one place I think; still, here it is: can't read "Cbg": no such variable can't read "Cbg": no such variable...
-
Yes, this problem arose when I started with both the "Ignore blanks when diffing" and "Suppress diffs of empty lines" Preference settings on and then toggled View->ShowChangeBars from off to on. The same thing happens if I toggle it in Preferences. Yes, it was after #61. That describes what I see immediately on startup. I forgot to supply the error details before, although Cbg occurs only in the one place I think; still, here it is: can't read "Cbg": no such variable can't read "Cbg": no such variable...
-
Yes, this problem arose when I started with both the "Ignore blanks when diffing" and "Suppress diffs of empty lines" Preference settings on and then toggled View->ShowChangeBars from off to on. The same thing happens if I toggle it in Preferences. Yes, it was after #61. That describes what I see immediately on startup. I forgot to supply the error details before, although Cbg occurs only in the one place I think; still, here it is: can't read "Cbg": no such variable can't read "Cbg": no such variable...
-
Application error (no such variable "Cbg") when trying to display change bars
-
Debatably erroneous display/emphasis of line number for ignored difference
-
Back at work and I've found one minor and one major issue with this for which I've opened new tickets.
-
It's ok, I don't for a moment expect anyone to try to fix bugs in old verions. I'm as frustrated by having to use 4.0.2 as you seem to be at getting bug reports for it. I entirely take your point about the newest tkdiff version clearly working in the being-migrated-to environment (Tk 8.5 and all) so I will see if I can find out who gets to decide when we should upgrade tkdiff. Still I am rather surprised that tkdiff is written to do anything other than interpret the diff output, which produces something...
-
We're (at work) only just about to trade up to 4.2, alas. We work on old OSes and s/w because that's what our customers still use, because they require ultra-stable systems. Sad but true. Regardless, on first impressions my private 4.3.5 still gets it wrong (although differently wrong). See new screenshot. Perhaps I need to look at the user settings. Update: the only other user setting that I could see was "ignore blank lines" and that made no difference. And FYI: diff (GNU diffutils) 3.3 Tk version...
-
We're (at work) only just about to trade up to 4.2, alas. We work on old OSes and s/w because that's what our customers still use, because they require ultra-stable systems. Sad but true. Regardless, on first impressions my private 4.3.5 still gets it wrong (although differently wrong). See new screenshot. Perhaps I need to look at the user settings. Update: the only other user setting that I could see was "ignore blank lines" and that made no difference.
-
We're (at work) only just about to trade up to 4.2, alas. We work on old OSes and s/w because that's what our customers still use, because they require ultra-stable systems. Sad but true. Regardless, on first impressions my private 4.3.5 still gets it wrong (although differently wrong). See new screenshot. Perhaps I need to look at the user settings.
-
tkdiff shows erroneous deletion when using diff -bwB
-
line highlighting doesn't honour ignore-whitespace-changes flag properly
1