Cool, thanks for doing this. (I like the Obsidian theme :)
Is it possible/necessary to apply any of the patches to the 0.4.7 beta release? (Although to be honest I can't recall any specific reason why I'm using that one.)
The new FBIde is no more compatible of this setting (from counting_pine):
- Leaving the command line window open when the program finishes
This basically consists of wrapping the Run command in "cmd /c [Run command] & pause", which opens up a command window which does the Run Command, and then run Pause to wait for a keypress before closing. This is a good alternative to putting Sleep at the end of a console program, and also stops the window closing if the program aborts with an error, allowing you to see the message returned. So it's good to use with '-exx' (not so useful with '-s gui').
Run command: cmd /c "<$file>" <$param> & pause
Error induced: execution of command failed (error 267)
fxm wrote:The new FBIde is no more compatible of this setting (from counting_pine):
- Leaving the command line window open when the program finishes
This basically consists of wrapping the Run command in "cmd /c [Run command] & pause", which opens up a command window which does the Run Command, and then run Pause to wait for a keypress before closing. This is a good alternative to putting Sleep at the end of a console program, and also stops the window closing if the program aborts with an error, allowing you to see the message returned. So it's good to use with '-exx' (not so useful with '-s gui').
Run command: cmd /c "<$file>" <$param> & pause
Error induced: execution of command failed (error 267)
If I replace the file 'FbIdeFix.dll' of this new version, by the file 'FbIdeFix.dll' associated with the previous patch 'fbide_fixed.exe', it runs with the '-exx runtime error' configuration:
Run command:
cmd /c "<$file>" <$param> & pause
Imortis - yeah hopefully. I've been working a bit. but we'll see.
counting_pine - patches are for 0.4.6 because its the "stable" release. the 0.4.7 is unfinished and buggy. Project support is half baked. I suppose some fixes will work with it and some won't be necessary.
fxm - thanks for reporting about the issues. We are looking to fix them and have a new release up soon.
When dragging the top of the view window up something goes wrong with repainting of the screen. It's as if the top of the result window functions clears the part of the screen it covers (turning it black). When going back down again and releasing the mouse the part of the screen that was black turns white again.
When I drag the top of the window completely down (all the way to the bottom of the desktop) the windows taskbar goes black as well. After a repaint the blackness disappears. Still, the screen should not turn black (should it?)
And now I am seeing the screen that's behind the fbide window when I drag the top of the result window. Really strange. Same thing happens when dragging the side of the sub/function browser.
Could this have something to do with the transparency 'features' of windows 7? I'm using windows 7 64bit (nvidia geforce gt 220).
