Re: Interface Resolution
Since it's just a stack, open it normally in LC. You can do that either from the Open file menu or since it's open already it should be in the Windows menu. Edit the script normally. Apply and save the stack. The next time LC starts up, the handlers should run. The plugin dialog only manages how and when the stack opens. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On October 16, 2020 11:05:17 AM John McKenzie via use-livecode wrote: Jacqueline, thank you for adding to my thread about the interface on 4k monitors. I did as suggested but there is no persistence with the plugins dialogue box. If there is a save, OK, or apply type functions I cannot find them. Closing the window does not appear to save the changes as there are not there later, including after quitting and restarting. After fooling around with it all your post caused me to think of it different and after a bit I got it working when picking my plugin from the development menu. That is to I run the IDE, go to the development menu and manually run my plugin script. Takes only a second so not bad. So getting it to run upon startup will be nice if I do, but I can live with this setup. Making the text in the drop down menus legible is something important I still have to do, but thanks to Jacqueline, Peter, Richard and Ralph for getting me to this mostly usable point. Work arounds are not as good as things working but having the ones I have make things better than before and good enough to have bought me time to get everything in good order. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Interface Resolution
Jacqueline, thank you for adding to my thread about the interface on 4k monitors. I did as suggested but there is no persistence with the plugins dialogue box. If there is a save, OK, or apply type functions I cannot find them. Closing the window does not appear to save the changes as there are not there later, including after quitting and restarting. After fooling around with it all your post caused me to think of it different and after a bit I got it working when picking my plugin from the development menu. That is to I run the IDE, go to the development menu and manually run my plugin script. Takes only a second so not bad. So getting it to run upon startup will be nice if I do, but I can live with this setup. Making the text in the drop down menus legible is something important I still have to do, but thanks to Jacqueline, Peter, Richard and Ralph for getting me to this mostly usable point. Work arounds are not as good as things working but having the ones I have make things better than before and good enough to have bought me time to get everything in good order. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Interface Resolution
Plugins are just normal stacks that appear in the plugins folder. When you open the stack, which opens automatically and invisibly on startup in this case, it will just sit there. It needs an activation handler, which can be on openstack or opencard or whatever is appropriate. Add whatever you need it to do in one of those handlers. In the plugin manager you'll see a list of special "rev" messages. This is an alternate way to trigger the actions the plugin should perform. Instead of using an openCard or preOpenCard handler, you can select the revPreOpenCard message from the list. That message will be sent to the plugin when it opens and if you have a handler in the stack with that name, it can perform the activities it needs to do. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On October 16, 2020 12:16:25 AM John McKenzie via use-livecode wrote: Never mind, I got the plugin to appear in the list in the plugins dialogue window. I selected it, set it to "LiveCode starts up" and "Invisible". Quit the IDE and restarted it. Nothing happens. Typing each command into the message box affects things though. I can kind of work with doing that while I try to find out the connection between the OS interface settings and Livecode reading them (if it does). One big issue still is the text on the drop down menus remains the same size. If anyone happens to know which file controls that I would be glad to hear the details. At some point I may scale each one of them one at a time until I discover what it is, if any. Maybe the font size is not even controlled by a stack script. Thanks for the help all that posted. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Interface Resolution
Never mind, I got the plugin to appear in the list in the plugins dialogue window. I selected it, set it to "LiveCode starts up" and "Invisible". Quit the IDE and restarted it. Nothing happens. Typing each command into the message box affects things though. I can kind of work with doing that while I try to find out the connection between the OS interface settings and Livecode reading them (if it does). One big issue still is the text on the drop down menus remains the same size. If anyone happens to know which file controls that I would be glad to hear the details. At some point I may scale each one of them one at a time until I discover what it is, if any. Maybe the font size is not even controlled by a stack script. Thanks for the help all that posted. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Interface Resolution
Ralph, thank for for the specific instructions. Thanks to the others and poking around I knew some of that, but the extra info was stuff I needed to know. Unfortunately, the script does not appear in the list of plugins in the Plugin Settings dialogue. Did basic things like double check the directory, quit and restarted the Livecode IDE, etc. Will keep following around with it, but if anyone has a theory off the top of their head for the lack of the plugin showing up I would like to hear it. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
RE: Interface Resolution
Put the commands you want to run in the preopen handler of your plug-in stack. Save the stack Close LC Put the stack into you're "My LiveCode/Plugins" folder. The location of this folder can be found in LC preferences in the "Files and Memory" section. Reopen LC Go to the Development==>Plugins and select(at the bottom) "Plugin Settings" Select your Plugin from the dropdown list In the "Open Plugin when:" section select "LiveCode starts up" In the "Open as" section select "Invisible" Restart LC and you should be good to go. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of John McKenzie via use-livecode Sent: Thursday, October 15, 2020 12:53 PM To: use-livecode@lists.runrev.com Cc: John McKenzie Subject: Re: Interface Resolution I felt up to trying one of the suggested workarounds for my interface scaling issue, specifically making a script to run as a plug-in. The plugin in does not appear on the plugins menu and I do not know what I did wrong. The link to creating plugins was helpful, but lacked specifics. Do I need to do something special to make it a plug-in? Such as having a shebang statement or a special command at the top declaring it a plug-in? Do it have to have a specific naming format? Should it begin or end with "rev" for example? I called it "intefaceScaling.livecode". Perhaps that was wrong to do. Looking at existing ones as examples I did not get the impression that was so. When I ran the command "put the stacks" it outputted the following. /opt/livecode/livecodecommunity-9.6.0.x86_64/Toolset/palettes/tools/revtools .livecodescript /opt/livecode/livecodecommunity-9.6.0.x86_64/Toolset/palettes/message box/revmessagebox.8.rev /opt/livecode/livecodecommunity-9.6.0.x86_64/Toolset/palettes/menubar/revmen ubar.livecodescript Do I need absolute filenames in my script? Do I need anything else in the script that makes up my plugin? Currently all I know to type is the following. set the scalefactor of stack "revtools" to 2 set the scalefactor of stack "revmessagebox.8" to 2 set the scalefactor of stack "revmenubar" to 2 Surely I need more than that. Sorry for my ignorance of what should be easy. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Interface Resolution
I felt up to trying one of the suggested workarounds for my interface scaling issue, specifically making a script to run as a plug-in. The plugin in does not appear on the plugins menu and I do not know what I did wrong. The link to creating plugins was helpful, but lacked specifics. Do I need to do something special to make it a plug-in? Such as having a shebang statement or a special command at the top declaring it a plug-in? Do it have to have a specific naming format? Should it begin or end with "rev" for example? I called it "intefaceScaling.livecode". Perhaps that was wrong to do. Looking at existing ones as examples I did not get the impression that was so. When I ran the command "put the stacks" it outputted the following. /opt/livecode/livecodecommunity-9.6.0.x86_64/Toolset/palettes/tools/revtools.livecodescript /opt/livecode/livecodecommunity-9.6.0.x86_64/Toolset/palettes/message box/revmessagebox.8.rev /opt/livecode/livecodecommunity-9.6.0.x86_64/Toolset/palettes/menubar/revmenubar.livecodescript Do I need absolute filenames in my script? Do I need anything else in the script that makes up my plugin? Currently all I know to type is the following. set the scalefactor of stack "revtools" to 2 set the scalefactor of stack "revmessagebox.8" to 2 set the scalefactor of stack "revmenubar" to 2 Surely I need more than that. Sorry for my ignorance of what should be easy. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Interface Resolution
Peter, thank you for those suggestions I will try them once my treatment is done tomorrow. Richard, I am using Kubunutu and KDE for some reason does not get every app when using its interface scaling setting. It gets almost all of them, but does not affect a few. It may be these apps are doing something wrong that the Livecode IDE does as well, but it is also possible it is a bug in KDE settings that only affects a handful of apps so it goes less noticed than it should be. So what I am saying is I will have to investigate more to see if it is the OS or the IDE that has a bug with scaling interfaces. A work around is good for now, but in general, yes, I should have something (in the OS or app) that just does it for the long term and that is worth investigating. BTW, I have greatly delayed working on the project that I thought Livecode could do well and brought me to it, mostly do to changes at work and health problems. This issue with the new monitor came up when I showed my brother the Livecode IDE and tell him about the platform. "Like Hypercard" really sucked him in, too. He was very interested and I may have gotten someone to try it out. Do not even have my own main app done and I recruited someone to try the platform. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Interface Resolution
These workarounds are great for helping John get back to work right away, but if the IDE isn't respecting Windows' resolution that would be a bug and I hope someone's reported it. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Interface Resolution
Hi John, I haven’t done this myself, but I suppose you could create a Livecode plugin that runs the needed code: https://livecode.fandom.com/wiki/Creating_a_livecode_plugin which is basically a LC stack that lives in your local plugins folder. Under the IDE Development menu are plugin settings, which includes an option, “Open plugin when: ‘LiveCode starts up.’” The plugin stack would have an openStack handler that calls the sizing handler. Or, you could have a script internal to your project that checks the environment property so it runs only when in the IDE. You might want to have a failsafe in case you have to run LC on a smaller monitor that would check the size of the monitor—the screenRect property—then size down the IDE elements appropriately. Peter > On Oct 14, 2020, at 10:09 PM, John McKenzie via use-livecode > wrote: > > > Peter, thank you for the information about changing the scale of the > IDE user interface. > > You mentioned that if I put a script somewhere to affect the IDE > stacks that it should work. I looked up the IDE stacks as per your > directions. Thanks for those. > > I do not know where a good somewhere to put such a script would be. Is > there a directory that gets its scripts execute upon running the IDE? > Or can I put it anywhere and take other action to have it run with the > IDE startup? > > Thanks. > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Interface Resolution
Peter, thank you for the information about changing the scale of the IDE user interface. You mentioned that if I put a script somewhere to affect the IDE stacks that it should work. I looked up the IDE stacks as per your directions. Thanks for those. I do not know where a good somewhere to put such a script would be. Is there a directory that gets its scripts execute upon running the IDE? Or can I put it anywhere and take other action to have it run with the IDE startup? Thanks. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Interface Resolution
Hi, You could use scaleFactor to resize the IDE elements, such as: set the scalefactor of stack "revtools" to 2 If you type into the message box: put the stacks you’ll get a list of the IDE stacks: /Applications/LiveCode Business 9.5.1.app/Contents/Tools/Toolset/palettes/message box/revmessagebox.8.rev /Applications/LiveCode Business 9.5.1.app/Contents/Tools/Toolset/palettes/menubar/revmenubar.livecodescript /Applications/LiveCode Business 9.5.1.app/Contents/Tools/Toolset/palettes/tools/revtools.livecodescript Having a script somewhere that sets the scaleFactor for each should do the trick. Peter Bogdanoff > On Oct 13, 2020, at 3:40 PM, John McKenzie via use-livecode > wrote: > > > Hello, all. > > I do not want to be asking this as it seems like something I can > easily look up, and it is a simple thing, but I am asking because I just > could not find out on my own despite trying. Trying allot at that. > > > The interface for the Livecode IDE is too small on my fancy, new 4k > monitor. I have changed OS settings to help with other programs and > it has for most of them. Some of the unaffected ones had built in > features to help with the interface resolution and others are still a > problem for me. > > Livecode is unaffected by everything. Would someone please tell me if > Livecode has anything inside it to change the IDE interface resolution > or if I have to depend on my operating system to take care of it? > > Livecode 9.6 build 15516 > Kubuntu 18.04.1 > > > Every reference I find talks about making your livecode stacks/apps > look better in 4k while all I care about right now is getting the IDE > to look legible at 4k. > > Thanks for any help provided. Sorry to ask something like this on the > list. > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
