<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thankyou for your reply</p>
<p>I suppose there are potentially many solutions I could look at
for my particular situation, one of those might be writing my own
private plugin which will give me the capability to get a toolbar
button from which it can then call my script if the script code is
copied into the plugin.</p>
<p>Questions are mostly along the lines</p>
<p>- are there any differences in the way a script interacts with a
running application when the script is incorporated into a plugin</p>
<p>- can a custom toolbar or button be added in the Layout window
(using the code example shown for ch16 of the pyqgis cookbook)</p>
<p>- can a script or plugin place a message in the message bar of a
Layout window instead of the main application window<br>
</p>
<div class="moz-cite-prefix">On 29/06/21 7:26 pm, Luigi Pirelli
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFO80_oExSSJYmf8fQxXfnDvjjHAoZRDA+A2a_JL1Wuh97sMsQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi Patrick
<div><br>
</div>
<div>seems more a question for the developer list where many UX
involved people can give you opinions.</div>
<div><br>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>Luigi Pirelli<br>
<br>
**************************************************************************************************<br>
* LinkedIn: <a
href="https://www.linkedin.com/in/luigipirelli"
target="_blank" moz-do-not-send="true">https://www.linkedin.com/in/luigipirelli</a><br>
* Stackexchange: <a
href="http://gis.stackexchange.com/users/19667/luigi-pirelli"
target="_blank" moz-do-not-send="true">http://gis.stackexchange.com/users/19667/luigi-pirelli</a><br>
* GitHub: <a
href="https://github.com/luipir"
target="_blank" moz-do-not-send="true">https://github.com/luipir</a><br>
* Book: <a
href="https://www.packtpub.com/eu/application-development/mastering-geospatial-development-qgis-3x-third-edition"
target="_blank" moz-do-not-send="true">Mastering
QGIS3 - 3rd Edition</a></div>
<div>* Hire a team: <a
href="http://www.qcooperative.net"
target="_blank" moz-do-not-send="true">http://www.qcooperative.net</a><br>
**************************************************************************************************</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, 29 Jun 2021 at 05:48,
Patrick Dunford <<a href="mailto:enzedrailmaps@gmail.com"
moz-do-not-send="true">enzedrailmaps@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Just
have a question here about the use of separate application
windows <br>
for the Qgis application main window and the Layout window.
Obviously <br>
the separate layout windows can be multiple in number whereas
most of <br>
the time we only need one application main window open.<br>
<br>
However for me there is the question of having different
toolbars and <br>
panels available in the two different types of window. Whilst
they do <br>
fulfill different functions of the application, the crossover
between <br>
those functions that is easy to achieve when running a script
somewhat <br>
blurs the merits of separate windows and raises the question
of why <br>
panels and toolbars can only be used in one or the other
windows but not <br>
both.<br>
<br>
In other words should you have the two distinct types of
window or one <br>
window that can have a combination of panels and toolbars from
anywhere. <br>
Granted that that would be a challenge if implemented to its
fullest <br>
extent since most of the panels and toolbars are specific to
each window <br>
type and the canvas would have to become some sort of panel as
well.<br>
<br>
My view on this is mostly driven by the apparently reasonable
conclusion <br>
that the Python scripting console panel should not be limited
to only <br>
being able to be docked to the application main window instead
of the <br>
layout window as is currently the case. I have a script that
performs a <br>
layout export to image and I have to keep switching backwards
and <br>
forwards between the main window and the layout window to run
the <br>
script, which can be for hundreds of export operations in a
day. The <br>
script itself reduces the number of mouse clicks needed to run
each of <br>
the individual exports by automatically selecting the layers
to make up <br>
an export in the main window.<br>
<br>
_______________________________________________<br>
Qgis-user mailing list<br>
<a href="mailto:Qgis-user@lists.osgeo.org" target="_blank"
moz-do-not-send="true">Qgis-user@lists.osgeo.org</a><br>
List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-user"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-user"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
</blockquote>
</div>
</blockquote>
</body>
</html>