Murga-Projects Forums

Full Version: [WIP] MurgaLua Reference Tool
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Ok, I see that too. Thanks for the report.
I think the widget is just being hidden, rather than removed, when notes are shown. That would mean the loop is still running and trying to make active a non-visible widget.
This will definitely have to be top priority.

BTW, draw-freehand-lines is one of those incomplete widgets that might end up being removed. It is essentially the same as draw-freehand anyway.

EDIT: It was a pretty easy fix. I separated the widget replace function into two parts: remove and replace. The remove function is now called from the text load function, so there shouldn't be anything running in the background when you view source. This change will appear in beta1. I can't say at this time if it might have created a new bug...will have to do more testing.
News: My hard drive is broken. I have no idea how long before I replace it, and then have no idea how much of its data can be salvaged. If I have to go back and pick up from the alpha stage again I will probably be kinda pissed and not want to do anything with it for a while.

With those three factors, I can't say with any level of certainty whether there will be an update soon (at least not until next year [giggle])
More news: I installed a new drive today, but it will still be a little while before I get back to dev. I wanted to install a newer version of Slackware on the new drive, but today realized that it no longer installs a graphical system with only one CD, so it will take a little while to get the rest of the installation disks.

After that works out, I still don't know if I'll be able to save the latest files from the old drive, so I might find myself repeating old changes.

mikshaw Wrote:
More news: I installed a new drive today, but it will still be a little while before I get back to dev. I wanted to install a newer version of Slackware on the new drive, but today realized that it no longer installs a graphical system with only one CD, so it will take a little while to get the rest of the installation disks.

After that works out, I still don't know if I'll be able to save the latest files from the old drive, so I might find myself repeating old changes.


Hey

I am very sad to hear all this, I am going to try and release version 0.6 this week
before you get things set up ... As most of the fixes affect FLTK and may help what
you are doing.

I am also sure you'll be happy to know the executable size has decreased a bit :-)

I have been pretty useless on the DEV front lately as work and my better half take
up almost all my time right now ...

However, a test version (0.6.5), will be out very soon too, and that IS bigger :-(

Cheers
JohnM

That's very good news. I'm happy you are continuing to develop this project regardless of the amount of time you get to work with it.

I installed DamnSmall Linux this morning from an older disk I had (last several releases have been direct install from the ISO rather than burning to disk), so I'm satisfied to use that exclusively until I get the rest of the Slackware setup. I like Grub (DSL's bootloader) better than lilo (Slack's bootloader) anyway, so having it already installed to use with Slack takes a little stress off me.

I might attempt to read my faulty drive later today, but the idea is still making me kind of nervous =o)
Update: I was able to save all my important data from the flaky drive. It seems that it was having lots of trouble writing, but not much trouble reading. I don't recall ever seeing that before, but I'm grateful for it.

Expect a beta within the next week or so.
I think i fixed the exiting or hiding on switching Widgets

Code:
function demo_replace_widget(new_file)
   -- remove previous widget
  if demo_widget then
  demo_widget:hide() -- hide it before removal
    demo_w:remove(demo_widget)
    Fl:delete_widget(demo_widget)
    demo_widget=nil
  end
  -- new child window for new widget
  demo_widget = fltk:Fl_Double_Window(0,demo_bh,demo_ww,demo_wh-demo_bh,demo_widget_files[i])
  dofile(new_file)
  fltk:Fl_End() -- end for each widget window
   demo_w:add(demo_widget)
   demo_widget:show()
   demo_w:redraw();
   demo_widget:make_current() -- needed for drawing functions
end


All I needed was one good sleepless night to allow me to have
more sleepless nights hacking this thing to do my bidding!

I'd already broken up this function into two parts in order to fix a crash mentioned earlier, so depending on what changes you've made (is it simply hiding the widget?) it may need a little more work. This is its current state, plus the hide line, though it hasn't been tested:

Code:
function demo_remove_widget()
  if demo_widget then
    demo_widget:hide() -- hide it before removal
    -- remove previous widget
    demo_w:remove(demo_widget)
    Fl:delete_widget(demo_widget)
    demo_widget=nil
  end
end

function demo_replace_widget(new_file)
  demo_remove_widget()
  -- new child window for new widget
demo_widget=fltk:Fl_Double_Window(0,demo_bh,demo_ww,demo_wh-demo_bh,demo_widget_files[i])
  dofile(new_file)
  fltk:Fl_End(demo_widget) -- end for each widget window
  demo_w:add(demo_widget)
  demo_widget:show()
  demo_widget:make_current() -- needed for drawing functions
end

yep that works!
Its just a case of hide before remove.
I've done some hacking with this, I'm using a separate window for the script.
Is there a way to pass that text to the clipboard very fast?
I can then leave the scripts hidden and just paste this magic stuff where needed.

Quote:
Is there a way to pass that text to the clipboard very fast?

I don't understand what text you mean, or what clipboard. It might be a OS specific thing? As the script is now, I believe you can save the text in the editing window to a file, but I haven't done any advanced Text_Editor features, even as simple as copy.

Pages: 1 2 3 4 5 6 7 8 9 10 11
Reference URL's