PureBasic 5.73 | SpiderBasic 2.30 | Windows 10 Pro (x64) | Linux Mint 20.1 (x64)
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.
PureBasic 5.73 | SpiderBasic 2.30 | Windows 10 Pro (x64) | Linux Mint 20.1 (x64)
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.
PureBasic 5.73 | SpiderBasic 2.30 | Windows 10 Pro (x64) | Linux Mint 20.1 (x64)
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.
Trond wrote:And what to do if the user presses cancel? (Then notepad does not exit.)
Well this is not that important to me because the user didn't wanted to save when cancelling, but at least he was asked to save...
If he doesn't want to save he clicks no. When he clicks cancel usually his changes are not lost, he can still save them after making additional changes.
This looks good to me, except one thing: notepad was just an example. Is there a more flexible way? Maybe replacing FindWindow_(@"notepad", 0) with a command that uses the number delivered from runprogram??
> Thanks a lot, maybe this example should be mentioned in the help file????
I don't understand... in one post you say it's NOT the number given by
RunProgram because you've tried it, but then you say the above when
an example is given where it IS the number given by RunProgram.
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.