Sketchup 8, serious observer bug?
-
@tig said:
It takes a blink of an eye to get / to set literally dozens of these settings as the web-dialog opens / closes. You could also make the dialog 'modal' so that the user can't close the model with the web-dialog open and thereby loose settings - I have done this because with my tool you can do several operations with the dialog remaining open and it's only on a 'close' that the current 'fields' get saved as attributes...
So what happens when the user tries to render/export with the settings dialog still open? I would like it to be possible not to have to close the dialog every time you want to render the scene, so it will be easy to make quick changes... I'm guessing you've probably handled it similar to me in that you have a temporary attribute dictionary, that gets save synced to sketchup on demand. So that it should be possible to export your scene whether the dialog is open or not... Either way, does implementing the "syncing" action in the deactivate(view) prevent it from being registered in the undo stack? Your solution to the problem does sound like it could work for me. Could I not also do it like like this? WebDialog.set_on_close{ save_settings(blabla)}
If I do it the way you suggested at least the user will will have the option to undo the changes, I just worry about it getting in the way of the modelling workflow, because it essentially creates a point where the user can no longer undo changes they made in the model. There really should be two undo stacks running in parallel
? -
do you have to write the settings to the model for every interaction you make to the model? what about writing them when your dialog closes?
-
@l.frisken said:
There really should be two undo stacks running in parallel
?I do think we should be able to make transactions that does not appear in the undo stack at all. At least set attributes. Because when you set model properties in SU you don't see them in the undo stack.
-
@thomthom said:
do you have to write the settings to the model for every interaction you make to the model? what about writing them when your dialog closes?
That's what I do - as you work the values can be read from the web-dialog as you go when you click some button it remembers the settings as attributes affected by that button.
The web-dialog has all of its fields available to be 'read' as you deactivate() so it can save all of them. if the users 'closes', or not if the users 'cancels' - but changes made during intermediate operations will be remembered as 'you go'... -
If i disable google update service and hide associated exe, i am experiencing noticable delay on closing sketchup or opening a new model.
First i thought i had AppObservr bugs.
Even though i try to code defensively against exceptions and presume surprises. -
@morisdov said:
If i disable google update service and hide associated exe, i am experiencing noticable delay on closing sketchup or opening a new model.
First i thought i had AppObservr bugs.
Even though i try to code defensively against exceptions and presume surprises.Yes! That's probably it. I'll check before I confirm that was my problem, but if it is then this is definitely google's responsibility. I do normally close the update service because I don't like to have random processes running in the background on my computer... But this definitely shouldn't affect sketchup usage!
-
I didn't think Google Update Service was related to SU... Thought it was SketchUp itself that did this check. I've only ever gotten update noticed when I've run SU.
-
A bit OT, but the right people seem to be here.
Are there any known problems with Settings?
The menu comes up OK and Render exports an LXS file, with a dialogue to start LuxRender, all good
But the Settings doesn't bring up anything at all?
SU8 Win7 64bit Lenovo Laptop ATI video card.<edit> i do have the SU2KT and SU2POV installed, so it may be some interference.
I don't want to uninstall these just yet as I'm finding both useful, but I will investigate ... -
ah mozzie,
It's actually not too OT at all
There are a number of known problems with SU2LUX's settings atm,
and I ran into this problem when trying to fix them.
If you want I can share what I have so far, and it should work
fine on SU7 and perhaps SU8 if the problem is restricted to
my machine but I suspect it isn't... (not that there is too much
to be desired in SU8 free anyway...) -
Well, I'm happy to test it out, on SU7 & 8 Pro. But programming? Nope.
But with TIG and ThomThom commenting here you've already got some deep SU Ruby knowledge.
If we can ask them to get involved ....As suggested, there's nice exporters for POVray and Kerkythea, which means we may be able to draw on others in the forums too.
Supporting another good OSF renderer in SU would be helpful to all involved.
What functions do you think needs to be done to move this project along, and then to the next level?
Advertisement