Bug in preview window and graph tab
- This topic has 10 replies, 2 voices, and was last updated 15 years, 4 months ago by
.
-
Posts
-
I’m using TimelineFX on my laptop at the moment – IntelGMA965.
I’ve found two things that aren’t right.
1. When I click on the Graph tab, it doesn’t work. Whichever tab I was on before remains. The horizontal/vertical scrollbars appear but the graph itself does not.
2. If I minimise TimelineFX to the taskbar, then go back to it, the black preview window is gone – there’s just a big grey area where it used to be.I tried an earlier version of TimelineFX on this laptop a couple of months back and it worked fine back then?
[edit] More info – a driver update fixed it partially. Now it all works fine unless I minimise the app to taskbar, after which the preview window and graph window don’t seem to be getting drawn any more.
Hey GfK, ok, I’m just trying to figure out what’s changed since the version it worked for you, which was version 1.01 I think? That was the version that implemented Bruceys patch to fix other people with the intel gfx who were crashing. Since 1.01 nothings changed as far as that’s concerned.
Ah, just read your edit, I wonder if there’s something I can do to reset things when a restore event happens… I’ll look into that, thanks!
More info regarding the graphs. Was just having a play and I noticed that the graph window does work ok, until I minimise the app, OR, if I change to another tab (i.e. shapes) then try to change back to the graph. It just stops getting redrawn.
The other three tabs continue to work perfectly – its just the graph one that doesn’t.
Ok, I’ve attached one of the max2d samples of wxWidgets, would you mind running it and letting me know if you get the same problems when minimising, or maybe even resizing? Thanks.
I think that works fine. I get a clock with black hands/numbers on a white background.
If I maximise the window, the white background doesn’t expand to fill the new window – it stays the same size as before and the new area around it is black. Is that what its meant to do?
If I minimise to taskbar, then maximise again, the clock is still running/being drawn correctly.
Tested this on my laptop (Intel GMA965) and my desktop (Nvidia 8500GT) – identical results on both.
Let me know if you need any more stuff testing.
Yeh that sounds like it works ok. I will do a new sample with 2 glCanvases and see if that replicates the issue.
Is the editor working ok on the Nvidia 8500GT?
Pete
The editor works fine on my 8500GT – no problems there.
Just tried the second gl test on my GMA965 – all is not well, I think?
When I first run it, both clocks are visible but only the right hand clock is updating. So I maximise it, still only the right hand clock is running.
If I “unmaximise” it, the left hand clock starts updating, and the right hand one stops. Maximise it again, and the left hand clock stops and the right one starts! If I minimise to taskbar at any point, then click the icon on the taskbar, whichever clock was running before I minimised is still running, and the other remains stopped.
Is this what you expected? Or are they both supposed to be constantly updating?
lol, bizzarre, they should both be updating at the same time, so it seems it’s struggling with updating 2 canvases at the same time. I’ll ask Brucey, see if he has any clues or possible workarounds, or maybe its a fix he can do for wxWidgets, thanks for the info. Worse case scenario is that I change the way the graph is drawn, ie., stop using a glCanvas there. It won’t look as nice but I’d prefer more stability ;).
I might put together a sample with MaxGUI (if I can remember how to use it!), be interesting if the same thing happens there…
No probs. Is there any reason you’re using GL over DX? I’ve always found DX to be much less of a ballache when it comes to compatibility.
I’ll do my best to get more testing done if you need it – just so you know my parents are over for the day tomorrow so it might be late afternoon before the PC even gets switched on. 🙂
[edit] Following on from the .eff crash bug thread – just updated to 1.05 and double checked this issue to make sure the bug still exists (or not) in that version. It does.
You must be logged in to reply to this topic.